A Data Security Finding describes detections or alerts generated by various data security products such as Data Loss Prevention (DLP), Data Classification, Secrets Management, Digital Rights Management (DRM), Data Security Posture Management (DSPM), and similar tools. These detections or alerts can be created using fingerprinting, statistical analysis, machine learning, or other methodologies.
The finding describes the actors and endpoints who accessed or own the sensitive data, as well as the resources which store the sensitive data.
Note: If the event producer is a security control, the <code>security_control</code> profile should be applied and its <code>attacks</code> information, if present, should be duplicated into the <code>finding_info</code> object.
Note: If the Finding is an incident, i.e., requires incident workflow, also apply the <code>incident</code> profile or aggregate this finding into an Incident Finding.
The action taken by a control or other policy-based system leading to an outcome or disposition. An unknown action may still correspond to a known disposition. Refer to disposition_id for the outcome of the action.
Group:context
Describes details about the actor implicated in the data security finding. Either an actor that owns a particular digital file or information store, or an actor which accessed classified or sensitive data.
Group:context
The normalized confidence refers to the accuracy of the rule that created the finding. A rule with a low confidence means that the finding scope is wide and may create finding reports that may not be malicious in nature.
Group:context
The Data Security object describes the characteristics, techniques and content of a Data Loss Prevention (DLP), Data Loss Detection (DLD), Data Classification, or similar tools' finding, alert, or detection mechanism(s).
Group:primary
Describes the database where classified or sensitive data is stored in, or was accessed from. Databases are typically datastore services that contain an organized collection of structured and/or semi-structured data.
Group:primary
Describes the databucket where classified or sensitive data is stored in, or was accessed from. The data bucket object is a basic container that holds data, typically organized through the use of data partitions.
Group:context
The additional information from an external data source, which is associated with the event or a finding. For example, add location information for the IP address in the DNS answers:
Group:context
The normalized impact of the incident or finding. Per NIST, this is the magnitude of harm that can be expected to result from the consequences of unauthorized disclosure, modification, destruction, or loss of information or information system availability.
Group:primary
Indicates that the event is considered to be an alertable signal. For example, an activity_id of 'Create' could constitute an alertable signal and the value would be true, while 'Close' likely would not and either omit the attribute or set its value to false. Note that other events with the security_control profile may also be deemed alertable signals and may also carry is_alert = true attributes.
Group:primary
The OSINT (Open Source Intelligence) object contains details related to an indicator such as the indicator itself, related indicators, geolocation, registrar information, subdomains, analyst commentary, and other contextual information. This information can be used to further enrich a detection or finding by providing decisioning support to other analysts and engineers.
The policy that pertains to the control that triggered the event, if applicable. For example the name of an anti-malware policy or an access control policy.
Describes details about additional resources, where classified or sensitive data is stored in, or was accessed from.
You can populate this object if the specific resource type objects available in the class (database, databucket, table, file) aren't sufficient; OR
You can also choose to duplicate uid, name of the specific resources objects, for a consistent access to resource uids across all findings.
Group:classification
The event/finding severity, normalized to the caption of the severity_id value. In the case of 'Other', it is defined by the source.
The normalized identifier of the event/finding severity.
The normalized severity is a measurement the effort and expense required to manage and resolve an event or incident. Smaller numerical values represent lower impact events, and larger numerical values represent higher impact events.
Group:context
The normalized status of the Finding set by the consumer normalized to the caption of the status_id value. In the case of 'Other', it is defined by the source.
Group:primary
Describes the table where classified or sensitive data is stored in, or was accessed from. The table object represents a table within a structured relational database, warehouse, lake, or similar.
Group:classification
The event/finding type ID. It identifies the event's semantics and structure. The value is calculated by the logging system as: class_uid * 100 + activity_id.
200600: Data Security Finding: Unknown (DATA_SECURITY_FINDING_UNKNOWN)
200601: Data Security Finding: Create (DATA_SECURITY_FINDING_CREATE)
200602: Data Security Finding: Update (DATA_SECURITY_FINDING_UPDATE)
200603: Data Security Finding: Close (DATA_SECURITY_FINDING_CLOSE)
200604: Data Security Finding: Suppressed (DATA_SECURITY_FINDING_SUPPRESSED)
200699: Data Security Finding: Other (DATA_SECURITY_FINDING_OTHER)
The Vendor Attributes object can be used to represent values of attributes populated by the Vendor/Finding Provider. It can help distinguish between the vendor-provided values and consumer-updated values of key attributes like severity_id.
The original finding producer should not populate this object. It should be populated by consuming systems that support data mutability.
