Policy Violations domain
All policy violation data, for all violations of the policy detected by the Guardium inspection engines or STAPs. This topic describes the domain's entities and attributes.
Available to roles: all
Client/Server Entity
This entity describes a specific client-server connection. An instance is created each time a unique set of attributes (excluding the Timestamp) is detected.
Client/Server By Session gets its count from the Client/Server and date conditions from the Session.
Client/Server gets its count from the Client/Server and date conditions also from the Client/Server.
If you select Client/Server, then the query is populated with ATTRIBUTE_ID = 1. If you select Client/Server By Session, then the query is populated with MAIN_ATTRIBUTE_ID = 0.
| Attribute | Description |
|---|---|
| Access ID | A unique identifier for this unique set of client/server connection attributes. Only available to users with the admin role. |
| Analyzed Client IP | Applies only to encrypted traffic; when set, client IP is set to
zeroes. Analyzed Client IP contains the IP for encrypted sessions. For unencrypted sessions Analyzed Client IP will be the same as Client IP. |
| Client Host Name | Client host name. |
| Client IP | Client IP address. For ASO traffic, CLIENT_IP is not the actual client IP; use the Analyzed Client IP, which is the correct IP. For Oracle ASO encrypted IPv6 traffic (local as well as remote), use the Client Host Name to identify the actual client session, due to limitations. For SSL traffic, Client IP is not the actual client IP and there is no Analyzed Client IP. |
| ClientIP / DBUser | Paired attribute value consisting of the client IP address and database user name. |
| Client IP/Src App/DB User/Server IP/Svc Name | A tuple group containing the named fields. For more information, see Tuple groups. |
| Client IP/Src App/User | A tuple group containing the named fields. For more information, see Tuple groups. |
| Client MAC | Client hardware address. |
| Client OS | Client operating system. For Teradata, as there is no direct information about client/server OS, instead, the data format type is used; indicating how integer data are stored during db session. This has a close relation to the platform being used and may appear as follows: IBM MAINFRAME // IBM mainframe data format HONEYWELL MAINFRAME // Honeywell mainframe data format AT&T 3B2 // AT&T 3B2 data format. INTEL 8086 // Intel 8086 data format (IBM PC or compatible) VAX // VAX data format AMDAHL // Amdahl data format |
| DB Protocol | Protocol specific to the database server For example, DRDA (Db2), TNS (Oracle), or TDS (MS SQL Server). |
| DB Protocol Version | Protocol version for the DB Protocol. |
| DB User Name | Database user name: user that connected to the database, either local or remote. |
| Last Used | The timestamp of the last time the data was used. |
| Network Protocol | Network protocol used (such as TCP or UDP. For K-TAP on Oracle, this displays as either IPC or BEQ) |
| OS User | OS user as reported by the database client where supported by the database type. |
| Server Description | Server description (if any). For example, displays cluster name of the Cloudera Data Platform. |
| Server Host Name | Server host name. |
| Server IP | Server IP address. |
| Server IP/DB user | Paired attribute value consisting of Server IP address and database user name. |
| Server IP/Svc Name/DB User | A tuple group containing the named fields. For more information, see Tuple groups. |
| Server OS | Server operating system. For Informix, the OS may appear as follows: IEEEM indicating Unix or JDBCIEEEI indicating WindowsDEC indicating DEC Alpha For Teradata, as there is no direct information about client/server OS, instead, the data format type is used; indicating how integer data are stored during db session. This has a close relation to the platform being used and may appear as follows: IBM MAINFRAME // IBM mainframe data format HONEYWELL MAINFRAME // Honeywell mainframe data format AT&T 3B2 // AT&T 3B2 data format. INTEL 8086 // Intel 8086 data format (IBM PC or compatible) VAX // VAX data format AMDAHL // Amdahl data format |
| Server Type | The type of database monitored, such as Dd2, Oracle, or Teradata. |
| Service Name | Service name for the interaction. In some cases (AIX shared memory connections, for example), the service name is an alias that
is used until the actual service is connected. In those cases, once the actual service is connected,
a new session is started - so what the user experiences as a single session is logged as two
sessions. For Teradata, Service name contains the session logical host id value. |
| Source Program | Source program as reported by the database client where supported by the database type. |
| Client/ Server by session | Client/Server by session is also a Main Entity. Access this secondary entity by clicking on the Client/Server primary entity. |
| Timestamp | The time on the collector when the client first connected to the server. For example, if a client is connecting to the server in the same way many days in a row this timestamp will be the time of the first connection. This may even be before the purge days of the appliance. |
| Timestamp Date | Date only from the timestamp. |
| Timestamp Time | Time only from the timestamp. |
| Timestamp Weekday | Weekday only from the timestamp. |
| Timestamp Year | Year only from the timestamp. |
Incident Status Entity
Describes the status of an Incident entity.
| Attribute | Description |
|---|---|
| Status Description | One of the following: OPEN - The incident has not yet been assigned to a user. ASSIGNED - The incident has been assigned. CLOSED - The incident is closed. |
Incident Severity Entity
The incident severity description for an incident.
| Attribute | Description |
|---|---|
| Incident Severity Description | Severity code, one of : INFO, LOW, MED, HIGH |
User Entity
Identifies the Guardium user defined as an audit process results receiver.
| Attribute | Description |
|---|---|
| EMAIL Address | Email address defined for the Guardium user. |
| First Name | First name for the Guardium user. |
| Last Active | Timestamp for last activity for this user. |
| Last Name | Last name for the Guardium user. |
| Login Name | Guardium user name. |
Session Entity
This entity is created for each Client/Server database session.
| Attribute | Description |
|---|---|
| Access ID | A unique identifier for this unique set of client/server connection attributes. Only available to users with the admin role. |
| Client Port | Client port number. |
| Database Name | Name of database for the session. For Oracle, Database Name may contain additional and application specific information such as the currently executing module for a session that has been set in the MODULE column of the V$SESSION view. |
| Duration (secs) | Indicates the length of time between the Session Start and the Session End (in seconds). |
| Global ID | Uniquely identifies the session - access. Only available to users with the admin role. |
| Ignored Since | Timestamp created when starting to ignore this session. |
| Inactive Flag |
|
| Old Session ID | Points to the session from which this session was created. Zero if this is the first session of the connection. |
| Original Timezone | The UTC offset. This is done in particular for aggregators that have
collectors in different time zones and so that activities that happened hours apart do not seem as
if they happened at the same time when imported to the aggregator. For instance, on an aggregator that aggregates data from different time zones, you can see session start of one record that is 21:00 with original timezone UTC-02:00 and another record where session start is 21:00 with original timezone UTC-05:00, This means that these events occurred 3 hours apart, but at the same respective local time (9 PM). |
| Process ID | The process ID of the client that initiated the connection (not always available). |
| Server Port | Server port number. |
| Session Encrypted | Whether the session is encrypted. 0: no; 1: yes. |
| Session End | The time on the DB server when the session ended. Session End is also a Main Entity. Access this secondary entity by clicking on the Session primary entity. |
| Session End Date | Date only from the Session End. |
| Session End Time | Time only from the Session End. |
| Session End Weekday | Weekday only from the Session End. |
| Session End Year | Year only from the Session End. |
| Session ID | Uniquely identifies the session. Only available to users with the admin role. |
| Session Ignored | A Yes indicates that the session was ignored using the IGNORE SESSION policy action. |
| Session Start | The time on the DB server when the session started. Session Start is also a Main Entity. Access this secondary entity by clicking on the Session primary entity. |
| Session Start Date | Date only from the Session Start. |
| Session Start Time | Time only from the Session Start. |
| Session Start Weekday | Weekday only from the Session Start. |
| Session Start Year | Year only from the Session Start. |
| Terminal Id | Terminal ID of the connection, used internally to resolve session information. |
| Timestamp | The time on the collector when the session information was most recently updated. Initially, a timestamp created for the first request on a client-server connection where there is not an active session in progress. Later, it is updated when the session is closed, or when it is marked inactive following an extended period of time with no observed activity. When tracking Session information, you are probably more interested in the Session Start and Session End attributes than the Timestamp attribute. If the session is closed it is be the same time as the Session End. |
| Timestamp Date | Date only from the timestamp. |
| Timestamp Time | Time only from the timestamp. |
| Timestamp Weekday | Weekday only from the timestamp. |
| Timestamp Year | Year only from the timestamp. |
| TTL | Only available to users with the admin role. |
| Uid Chain | For a session reported by Unix S-TAP (K-TAP mode only), or
FAM on Windows, this shows the chain of OS users, when users su with a different
user name. For more information, see Linux-Unix: UID
chains and UID chain for
FAM. |
| Uid Chain Compressed | The UID chain excluding the first user and the last user. For more information, see Linux-Unix: UID chains and UID chain for FAM. |
Severity Entity
The incident severity for an incident or policy violation
| Attribute | Description |
|---|---|
| Severity Description | The severity code is one of: INFO, LOW, MED, HIGH |
Incident Entity
Incident entities are created by incident generation processes, or manually by assigning a policy violation to an incident.
| Attribute | Description |
|---|---|
| Category Name | Category assigned to the incident. |
| Incident Number | Incident number (assigned sequentially). |
| Timestamp | Time the incident was created. |
Client/Server Session Entity
| Attribute | Description |
|---|---|
| Client IP/Src App/DB User/Server IP/Svc. Name/OS User/DB Name | A tuple group containing the named fields. For more information, see Tuple groups. |
| Server IP/Server Port | Server IP/Server Port |
Policy Rule Violation Entity
This entity is created each time that a policy rule violation is logged. Not all policy rule violations are logged, see the description of the rule actions in Policy rule actions. The access rule causing the violation are available in the dependent Access Rule Entity (described earlier).
| Attribute | Description |
|---|---|
| Application Event Id | Application event ID (if any - these are set using the application events API) |
| Application User Name | Name of the user creating the policy rule violation. |
| Access Rule Description | The description of the rule from its definition. |
| Category Name | Category defined for the rule. |
| Classification Name | Name of classification process. |
| CLS Process Run ID | Classification process job execution ID. |
| Construct ID | Uniquely identifies the construct in which it was referenced. |
| Full SQL String | SQL string causing the policy rule violation. |
| Incident Number | If assigned to an incident, this is the incident number. |
| Message Sent | The text of the policy rule violation message that was sent. |
| Original Timezone | The UTC offset. This is done in particular for aggregators that have
collectors in different time zones and so that activities that happened hours apart do not seem as
if they happened at the same time when imported to the aggregator. For instance, on an aggregator that aggregates data from different time zones, you can see session start of one record that is 21:00 with original timezone UTC-02:00 and another record where session start is 21:00 with original timezone UTC-05:00, This means that these events occurred 3 hours apart, but at the same respective local time (9 PM). |
| Severity | Severity defined for the rule (the severity of an incident to which this is assigned may be different). |
| Timestamp | The time on the DB Server that the SQL triggering a policy violation was executed. Traffic must be captured with an alerting policy action to see this timestamp. |
| Timestamp Date | Date only from the timestamp. |
| Timestamp Time | Time only from the timestamp. |
| Timestamp Weekday | Weekday only from the timestamp. |
| Timestamp Year | Year only from the timestamp. |
| Total Occurrences | Occurrence count that triggered the violation. |
| Violation Log Id | Uniquely identifies the violation entity. Only available to users with the admin role. |
Application Events Entity
This entity is created each time that the system observes an Application Events API call (which sets these attribute values) or a stored procedure call that has been identified as a Custom Identification Procedure (which maps stored procedure parameters to these attributes).
| Attribute | Description |
|---|---|
| Application Event ID | Unique identifier for this application events entity. Only available to users with the admin role. |
| Event Date | Datetime value, set by GuardAppEvent:Start. It displays in the format
yyyy-mm-dd hh:mm:ss. Note: If an attempt is made to set the event date using a format other than
yyyy-mm-dd, it will contain all zeroes. The time portion (hh:mm:ss) is optional, and if omitted will
be 00:00:00.
|
| Event Release Date | Datetime value, set by GuardAppEvent:Released. It displays in the format yyyy-mm-dd hh:mm:ss. |
| Event Release Type | Type of event, set by GuardAppEvent: Released. |
| Event Release User Name | User name, set by GuardAppEvent: Released. |
| Event Release Value Num | Numeric value, set by GuardAppEvent: Released. |
| Event Release Value Str | String value, set by GuardAppEvent: Released. |
| Event Type | Type of event, set by GuardAppEvent:Start. |
| Event User Name | User name, set by GuardAppEvent:Start. |
| Event Value Str | String value, set by GuardAppEvent:Start. |
| Event Value Num | Numeric value, set by GuardAppEvent:Start. |
| Original Timezone | The UTC offset. This is done in particular for aggregators that have
collectors in different time zones and so that activities that happened hours apart do not seem as
if they happened at the same time when imported to the aggregator. For instance, on an aggregator that aggregates data from different time zones, you can see session start of one record that is 21:00 with original timezone UTC-02:00 and another record where session start is 21:00 with original timezone UTC-05:00, This means that these events occurred 3 hours apart, but at the same respective local time (9 PM). |
| Timestamp | Created only once, when the event is logged. Do not confuse this attribute with the Event Date attribute, which can be set using an API call or from a stored procedure parameter. (See a description of the Application Events API in Identify Users with API.) |
SQL Entity
This entity is created for each unique string of SQL. Values are replaced by question marks - only the format of the string is stored.
| Attribute | Description |
|---|---|
| Bind Info | Bind information for this SQL string. |
| Construct ID | Uniquely identifies the construct in which the SQL appeared |
| Sql | SQL string. |
| Truncated SQL | Indicates if the SQL has been truncated or not where: 0 - false/no, not truncated 1 - true/yes, truncated |
Command Entity
For each command, an entity is created for each parent node and position in which the command appears in a command construct.
| Attribute | Description |
|---|---|
| Command Id | Uniquely identifies the command. Only available to users with the admin role. |
| Construct Id | Uniquely identifies the construct (e.g., select a from b). Only available to users with the admin role. |
| Depth | Depth of the command in the SQL parse tree. |
| Parent | Identifier of parent node in the parse tree. |
| SQL Verb | Main verb in SQL command (e.g., select, insert, delete, etc.). |
Object Entity
An instance of this entity is created for each object in a unique schema.
| Attribute | Description |
|---|---|
| App Object Module1 | Uniquely identifies the application object module. |
| Construct Id | Uniquely identifies the construct in which the object is referenced. Only available to users with the admin role. |
| Object Id | Uniquely identifies the object. Only available to users with the admin role. |
| Object Name | Name of the object. |
| Schema | Database schema for the object. Note: This attribute is deprecated since it is
never populated
|
Field Entity
Each time Guardium encounters a new field, it creates a field entity.
| Attribute | Description |
|---|---|
| Command ID | Uniquely identifies the main command from the construct in which it was referenced. Only available to users with the admin role. |
| Construct ID | Uniquely identifies the construct in which it was referenced. Only available to users with the admin role. |
| Field ID | Uniquely identifies the field. Only available to users with the admin role. |
| Field Name | Name of the field. |
| List Clause Where Clause Order by Clause Having Clause Group By Clause On Clause |
Use these attributes to order complex SQL queries. Example of SQL queries: Order by SELECT * FROM dept_costs WHERE dept_total > (SELECT avg FROM avg_cost) ORDER BY department Having SELECT column_name1, SUM(column_name2) FROM table_name GROUP BY column_name1 HAVING (numerical function condition) Group By SELECT column_name1, SUM(column_name2) FROM table_name GROUP BY column_name1 Where SELECT FirstName, LastName, City FROM Users WHERE City = Los Angeles |
| Object ID | Uniquely identifies the object from the construct in which it was referenced. Only available to users with the admin role. |