ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

PIM/PAMSC: note on SPECIALPGM class in Reference Guide


Article ID: 140966


Updated On:


CA Virtual Privilege Manager CA Privileged Identity Management Endpoint (PIM) CA Privileged Access Manager - Server Control (PAMSC)


following note can be found in SPECIAL PGM description in manual page:

for example, PIM r12.8 SP1 manual 




You cannot define a record in the SPECIALPGM class for incoming network interception events.

 This is because the incoming network interception event does not have a process name in this

 context. To bypass writing an audit record for the interception event, set the AUDIT property to

 NONE for the corresponding record in the TCP class


But incoming and outgoing network event can be bypassed by SPECIALPGM rule. 


Release : 12.8

Component : CA ControlMinder - Unix


This note is for only Windows class at all PIM/PAMSC version.

Because audit log for incoming network event shows as following on Windows:

  28 Nov 2019 17:43:15 P TCP (Inbound) microsoft-ds  408  3 remote-client



Additional Information

On UNIX environment, audit log is shown as following:

  28 Nov 2019 03:27:54 P TCP          ssh                  404  3 remote-client        /usr/sbin/sshd

It shows process name and it should by bypass by SPECIALGPM class.