Skip to content

Data Security Finding (2006)

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 security_control profile should be applied and its attacks information, if present, should be duplicated into the finding_info object. Note: If the Finding is an incident, i.e. requires incident workflow, also apply the incident profile or aggregate this finding into an Incident Finding.

  • Category: Findings
  • Extends: finding
  • UID: 2006

Attributes

Section titled “Attributes”

Classification

Section titled “Classification”

activity_id

  • Type: integer_t
  • Requirement: required
  • Values:
    • 0 - Unknown: The event activity is unknown.
    • 1 - Create: A new Data Security finding is created.
    • 2 - Update: An existing Data Security finding is updated with more information.
    • 3 - Close: An existing Data Security finding is closed, this can be due to any resolution (e.g., True Positive, False Positive, etc.).
    • 4 - Suppressed: An existing Data Security finding is suppressed due to inaccurate detection techniques or a known true negative.
    • 99 - Other: The event activity is not mapped. See the activity_name attribute, which contains a data source specific value.

The normalized identifier of the Data Security Finding activity.

category_uid

  • Type: integer_t
  • Requirement: required
  • Values:
    • 2 - Findings: Findings events report findings, detections, and possible resolutions of malware, anomalies, or other actions performed by security products.

The category unique identifier of the event.

class_uid

  • Type: integer_t
  • Requirement: required
  • Values:
    • 2006 - Data Security Finding: 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 security_control profile should be applied and its attacks information, if present, should be duplicated into the finding_info object. Note: If the Finding is an incident, i.e. requires incident workflow, also apply the incident profile or aggregate this finding into an Incident Finding.

The unique identifier of a class. A class describes the attributes available in an event.

severity_id

  • Type: integer_t
  • Requirement: required
  • Values:
    • 0 - Unknown: The event/finding severity is unknown.
    • 1 - Informational: Informational message. No action required.
    • 2 - Low: The user decides if action is needed.
    • 3 - Medium: Action is required but the situation is not serious at this time.
    • 4 - High: Action is required immediately.
    • 5 - Critical: Action is required immediately and the scope is broad.
    • 6 - Fatal: An error occurred but it is too late to take remedial action.
    • 99 - Other: The event/finding severity is not mapped. See the severity attribute, which contains a data source specific value.

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.

type_uid

  • Type: long_t
  • Requirement: required
  • Values:
    • 200600 - Data Security Finding: Unknown
    • 200601 - Data Security Finding: Create: A new Data Security finding is created.
    • 200602 - Data Security Finding: Update: An existing Data Security finding is updated with more information.
    • 200603 - Data Security Finding: Close: An existing Data Security finding is closed, this can be due to any resolution (e.g., True Positive, False Positive, etc.).
    • 200604 - Data Security Finding: Suppressed: An existing Data Security finding is suppressed due to inaccurate detection techniques or a known true negative.
    • 200699 - Data Security Finding: Other

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.

activity_name

  • Type: string_t
  • Requirement: optional

The Data Security finding activity name, as defined by the activity_id.

category_name

  • Type: string_t
  • Requirement: optional

The event category name, as defined by category_uid value: Findings.

class_name

  • Type: string_t
  • Requirement: optional

The event class name, as defined by class_uid value: Data Security Finding.

severity

  • Type: string_t
  • Requirement: optional

The event/finding severity, normalized to the caption of the severity_id value. In the case of ‘Other’, it is defined by the source.

type_name

  • Type: string_t
  • Requirement: optional

The event/finding type name, as defined by the type_uid.

Context

Section titled “Context”

metadata

The metadata associated with the event or a finding.

actor

  • Type: actor
  • Requirement: recommended

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.

confidence_id

  • Type: integer_t
  • Requirement: recommended
  • Values:
    • 0 - Unknown: The normalized confidence is unknown.
    • 1 - Low
    • 2 - Medium
    • 3 - High
    • 99 - Other: The confidence is not mapped to the defined enum values. See the confidence attribute, which contains a data source specific value.

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.

data_security

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).

device

  • Type: device
  • Requirement: recommended

Describes the device where classified or sensitive data is stored in, or was accessed from.

dst_endpoint

Describes the endpoint where classified or sensitive data is stored in, or was accessed from.

priority_id incident

  • Type: integer_t
  • Requirement: recommended
  • Values:
    • 0 - Unknown: No priority is assigned.
    • 1 - Low: Application or personal procedure is unusable, where a workaround is available or a repair is possible.
    • 2 - Medium: Non-critical function or procedure is unusable or hard to use causing operational disruptions with no direct impact on a service’s availability. A workaround is available.
    • 3 - High: Critical functionality or network access is interrupted, degraded or unusable, having a severe impact on services availability. No acceptable alternative is possible.
    • 4 - Critical: Interruption making a critical functionality inaccessible or a complete network interruption causing a severe impact on services availability. There is no possible alternative.
    • 99 - Other: The priority is not normalized.

The normalized priority. Priority identifies the relative importance of the incident or finding. It is a measurement of urgency.

src_endpoint

Details about the source endpoint where classified or sensitive data was accessed from.

status_id

  • Type: integer_t
  • Requirement: recommended
  • Values:
    • 0 - Unknown: The status is unknown.
    • 1 - New: The Finding is new and yet to be reviewed.
    • 2 - In Progress: The Finding is under review.
    • 3 - Suppressed: The Finding was reviewed, determined to be benign or a false positive and is now suppressed.
    • 4 - Resolved: The Finding was reviewed, remediated and is now considered resolved.
    • 5 - Archived: The Finding was archived.
    • 99 - Other: The event status is not mapped. See the status attribute, which contains a data source specific value.

The normalized status identifier of the Finding, set by the consumer.

api cloud

  • Type: api
  • Requirement: optional

Describes details about a typical API (Application Programming Interface) call.

assignee incident

  • Type: user
  • Requirement: optional

The details of the user assigned to an Incident.

assignee_group incident

  • Type: group
  • Requirement: optional

The details of the group assigned to an Incident.

comment

  • Type: string_t
  • Requirement: optional

A user provided comment about the finding.

confidence

  • Type: string_t
  • Requirement: optional

The confidence, normalized to the caption of the confidence_id value. In the case of ‘Other’, it is defined by the event source.

confidence_score

  • Type: integer_t
  • Requirement: optional

The confidence score as reported by the event source.

enrichments

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:[{"name": "answers.ip", "value": "92.24.47.250", "type": "location", "data": {"city": "Socotra", "continent": "Asia", "coordinates": [-25.4153, 17.0743], "country": "YE", "desc": "Yemen"}}]

impact

  • Type: string_t
  • Requirement: optional

The impact , normalized to the caption of the impact_id value. In the case of ‘Other’, it is defined by the event source.

impact_id

  • Type: integer_t
  • Requirement: optional
  • Values:
    • 0 - Unknown: The normalized impact is unknown.
    • 1 - Low: The magnitude of harm is low.
    • 2 - Medium: The magnitude of harm is moderate.
    • 3 - High: The magnitude of harm is high.
    • 4 - Critical: The magnitude of harm is high and the scope is widespread.
    • 99 - Other: The impact is not mapped. See the impact attribute, which contains a data source specific value.

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.

impact_score

  • Type: integer_t
  • Requirement: optional

The impact as an integer value of the finding, valid range 0-100.

is_suspected_breach incident

  • Type: boolean_t
  • Requirement: optional

A determination based on analytics as to whether a potential breach was found.

priority incident

  • Type: string_t
  • Requirement: optional

The priority, normalized to the caption of the priority_id value. In the case of ‘Other’, it is defined by the event source.

raw_data

  • Type: string_t
  • Requirement: optional

The raw event/finding data as received from the source.

risk_details

  • Type: string_t
  • Requirement: optional

Describes the risk associated with the finding.

risk_level

  • Type: string_t
  • Requirement: optional

The risk level, normalized to the caption of the risk_level_id value.

risk_level_id

  • Type: integer_t
  • Requirement: optional
  • Values:
    • 0 - Info
    • 1 - Low
    • 2 - Medium
    • 3 - High
    • 4 - Critical
    • 99 - Other: The risk level is not mapped. See the risk_level attribute, which contains a data source specific value.

The normalized risk level id.

risk_score

  • Type: integer_t
  • Requirement: optional

The risk score as reported by the event source.

status

  • Type: string_t
  • Requirement: optional

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.

ticket incident

  • Type: ticket
  • Requirement: optional

The linked ticket in the ticketing system.

unmapped

  • Type: object
  • Requirement: optional

The attributes that are not mapped to the event schema. The names and values of those attributes are specific to the event source.

vendor_attributes

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-prodvided 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.

Occurrence

Section titled “Occurrence”

time

  • Type: timestamp_t
  • Requirement: required

The normalized event occurrence time or the finding creation time.

timezone_offset

  • Type: integer_t
  • Requirement: recommended

The number of minutes that the reported event time is ahead or behind UTC, in the range -1,080 to +1,080.

count

  • Type: integer_t
  • Requirement: optional

The number of times that events in the same logical group occurred during the event Start Time to End Time period.

duration

  • Type: long_t
  • Requirement: optional

The event duration or aggregate time, the amount of time the event covers from start_time to end_time in milliseconds.

end_time

  • Type: timestamp_t
  • Requirement: optional

The time of the most recent event included in the finding.

end_time_dt datetime

  • Type: datetime_t
  • Requirement: optional

The time of the most recent event included in the finding.

start_time

  • Type: timestamp_t
  • Requirement: optional

The time of the least recent event included in the finding.

start_time_dt datetime

  • Type: datetime_t
  • Requirement: optional

The time of the least recent event included in the finding.

time_dt datetime

  • Type: datetime_t
  • Requirement: optional

The normalized event occurrence time or the finding creation time.

Primary

Section titled “Primary”

cloud cloud

  • Type: cloud
  • Requirement: required

Describes details about the Cloud environment where the event was originally created or logged.

finding_info

Describes the supporting information about a generated finding.

osint osint

  • Type: osint
  • Requirement: required

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.

action_id security_control

  • Type: integer_t
  • Requirement: recommended
  • Values:
    • 0 - Unknown: The action was unknown. The disposition_id attribute may still be set to a non-unknown value, for example ‘Custom Action’, ‘Challenge’.
    • 1 - Allowed: The activity was allowed. The disposition_id attribute should be set to a value that conforms to this action, for example ‘Allowed’, ‘Approved’, ‘Delayed’, ‘No Action’, ‘Count’ etc.
    • 2 - Denied: The attempted activity was denied. The disposition_id attribute should be set to a value that conforms to this action, for example ‘Blocked’, ‘Rejected’, ‘Quarantined’, ‘Isolated’, ‘Dropped’, ‘Access Revoked, etc.
    • 3 - Observed: The activity was observed, but neither explicitly allowed nor denied. This is common with IDS and EDR controls that report additional information on observed behavior such as TTPs. The disposition_id attribute should be set to a value that conforms to this action, for example ‘Logged’, ‘Alert’, ‘Detected’, ‘Count’, etc.
    • 4 - Modified: The activity was modified, adjusted, or corrected. The disposition_id attribute should be set appropriately, for example ‘Restored’, ‘Corrected’, ‘Delayed’, ‘Captcha’, ‘Tagged’.
    • 99 - Other: The action is not mapped. See the action attribute which contains a data source specific value.

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.

database

  • Type: database
  • Requirement: recommended

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.

databucket

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.

disposition_id security_control

  • Type: integer_t
  • Requirement: recommended
  • Values:
    • 0 - Unknown: The disposition is unknown.
    • 1 - Allowed: Granted access or allowed the action to the protected resource.
    • 2 - Blocked: Denied access or blocked the action to the protected resource.
    • 3 - Quarantined: A suspicious file or other content was moved to a benign location.
    • 4 - Isolated: A session was isolated on the network or within a browser.
    • 5 - Deleted: A file or other content was deleted.
    • 6 - Dropped: The request was detected as a threat and resulted in the connection being dropped.
    • 7 - Custom Action: A custom action was executed such as running of a command script. Use the message attribute of the base class for details.
    • 8 - Approved: A request or submission was approved. For example, when a form was properly filled out and submitted. This is distinct from 1 ‘Allowed’.
    • 9 - Restored: A quarantined file or other content was restored to its original location.
    • 10 - Exonerated: A suspicious or risky entity was deemed to no longer be suspicious (re-scored).
    • 11 - Corrected: A corrupt file or configuration was corrected.
    • 12 - Partially Corrected: A corrupt file or configuration was partially corrected.
    • 13 - Uncorrected: A corrupt file or configuration was not corrected.
    • 14 - Delayed: An operation was delayed, for example if a restart was required to finish the operation.
    • 15 - Detected: Suspicious activity or a policy violation was detected without further action.
    • 16 - No Action: The outcome of an operation had no action taken.
    • 17 - Logged: The operation or action was logged without further action.
    • 18 - Tagged: A file or other entity was marked with extended attributes.
    • 19 - Alert: The request or activity was detected as a threat and resulted in a notification but request was not blocked.
    • 20 - Count: Counted the request or activity but did not determine whether to allow it or block it.
    • 21 - Reset: The request was detected as a threat and resulted in the connection being reset.
    • 22 - Captcha: Required the end user to solve a CAPTCHA puzzle to prove that a human being is sending the request.
    • 23 - Challenge: Ran a silent challenge that required the client session to verify that it’s a browser, and not a bot.
    • 24 - Access Revoked: The requestor’s access has been revoked due to security policy enforcements. Note: use the Host profile if the User or Actor requestor is not present in the event class.
    • 25 - Rejected: A request or submission was rejected. For example, when a form was improperly filled out and submitted. This is distinct from 2 ‘Blocked’.
    • 26 - Unauthorized: An attempt to access a resource was denied due to an authorization check that failed. This is a more specific disposition than 2 ‘Blocked’ and can be complemented with the authorizations attribute for more detail.
    • 27 - Error: An error occurred during the processing of the activity or request. Use the message attribute of the base class for details.
    • 99 - Other: The disposition is not mapped. See the disposition attribute, which contains a data source specific value.

Describes the outcome or action taken by a security control, such as access control checks, malware detections or various types of policy violations.

file

  • Type: file
  • Requirement: recommended

Describes a file that contains classified or sensitive data.

is_alert

  • Type: boolean_t
  • Requirement: recommended

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.

message

  • Type: string_t
  • Requirement: recommended

The description of the event/finding, as defined by the source.

observables

The observables associated with the event or a finding.

resources

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.

src_url incident

  • Type: url_t
  • Requirement: recommended

A Url link used to access the original incident.

status_code

  • Type: string_t
  • Requirement: recommended

The event status code, as reported by the event source.

For example, in a Windows Failed Authentication event, this would be the value of ‘Failure Code’, e.g. 0x18.

status_detail

  • Type: string_t
  • Requirement: recommended

The status detail contains additional information about the event/finding outcome.

table

  • Type: table
  • Requirement: recommended

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.

verdict incident

  • Type: string_t
  • Requirement: recommended

The verdict assigned to an Incident finding.

verdict_id incident

  • Type: integer_t
  • Requirement: recommended
  • Values:
    • 0 - Unknown: The type is unknown.
    • 1 - False Positive: The incident is a false positive.
    • 2 - True Positive: The incident is a true positive.
    • 3 - Disregard: The incident can be disregarded as it is unimportant, an error or accident.
    • 4 - Suspicious: The incident is suspicious.
    • 5 - Benign: The incident is benign.
    • 6 - Test: The incident is a test.
    • 7 - Insufficient Data: The incident has insufficient data to make a verdict.
    • 8 - Security Risk: The incident is a security risk.
    • 9 - Managed Externally: The incident remediation or required actions are managed externally.
    • 10 - Duplicate: The incident is a duplicate.
    • 99 - Other: The type is not mapped. See the type attribute, which contains a data source specific value.

The normalized verdict of an Incident.

action security_control

  • Type: string_t
  • Requirement: optional

The normalized caption of action_id.

attacks security_control

  • Type: attack
  • Requirement: optional

An array of MITRE ATT&CK® objects describing identified tactics, techniques & sub-techniques.

authorizations security_control

Provides details about an authorization, such as authorization outcome, and any associated policies related to the activity/event.

disposition security_control

  • Type: string_t
  • Requirement: optional

The disposition name, normalized to the caption of the disposition_id value. In the case of ‘Other’, it is defined by the event source.

firewall_rule security_control

The firewall rule that pertains to the control that triggered the event, if applicable.

malware security_control

  • Type: malware
  • Requirement: optional

A list of Malware objects, describing details about the identified malware.

policy security_control

  • Type: policy
  • Requirement: optional

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.

Objects Used

Section titled “Objects Used”