PIM/PAMSC: note on SPECIALPGM class in Reference Guide

Products

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

Issue/Introduction

The following note can be found in SPECIALPGM description in the manual page:

for example, PIM r12.8 SP1 manual 

SPECIALPGM Class

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-controlminder/12-8-01/reference/selang-reference-guide/classes-in-the-ac-environment/specialpgm-class.html

...

Note:

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. 

Environment

Release : 12.8

Component : CA ControlMinder - Unix

Resolution

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

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.