Fortinet black logo

online help

SOX-COBIT - Access to Sensitive Data

SOX-COBIT - Access to Sensitive Data

Description

Access to Sensitive Data policy monitors and tracks access to sensitive data located in the cloud account. Sensitive data location can be configured through file path Regex.

Policy Configuration

Follow the steps below to enable and configure the policy

  1. Click on any Cloud Account drop down menu from FortiCASB dashboard, e.g. Salesforce, Office365, etc.
  2. Click on Policy drop down menu and select Compliance, then select PCI-DSS tab.
  3. Locate Access to Sensitive Data and click on the right arrow key > button to expand the policy.
  4. Click on General tab, click Status toggle switch button to enable the policy.
  5. Click on Severity level drop down menu to select the severity level (Critical, Alert, Warning, Information).
  6. Note: this policy generates both alert in Alert page and data in Compliance Report.

  7. Click Context tab to configure settings.
  8. In File Path Regex, enter a valid Regex of the target file path to be monitored. Here are examples of file path Regex:
    1. ".*" targets all files in the cloud account.
    2. "^(?:[\w]\:|\\)(\\[a-z_\-\s0-9\.]+)+\.(txt|gif|pdf|doc|docx|xls|xlsx)$" targets files begin with x:\ or \\ with files ending in the following types of extensions: txt, gif, pdf, doc, docx, xls, xlsx. Here are the file paths that will this file path Regex matches:
      1. \\192.168.0.1\folder\file.pdf
      2. c:\my folder\abc abc.docx

    Reference:

    https://www.codeproject.com/Tips/216238/Regular-Expression-to-Validate-File-Path-and-Exten

  9. In Data Patterns, click on the field and select the data patterns (financial, personal identity information, etc.) to be monitored.
  10. Click Save to upgrade the configuration.

After the policy is enabled and configured, whenever any targeted sensitive file is accessed, an alert will be triggered in the alert page. For more details, please refer to Alert.

Compliance report will also record any alerts generated by this policy, for more details, please see Compliance Report.

SOX-COBIT - Access to Sensitive Data

Description

Access to Sensitive Data policy monitors and tracks access to sensitive data located in the cloud account. Sensitive data location can be configured through file path Regex.

Policy Configuration

Follow the steps below to enable and configure the policy

  1. Click on any Cloud Account drop down menu from FortiCASB dashboard, e.g. Salesforce, Office365, etc.
  2. Click on Policy drop down menu and select Compliance, then select PCI-DSS tab.
  3. Locate Access to Sensitive Data and click on the right arrow key > button to expand the policy.
  4. Click on General tab, click Status toggle switch button to enable the policy.
  5. Click on Severity level drop down menu to select the severity level (Critical, Alert, Warning, Information).
  6. Note: this policy generates both alert in Alert page and data in Compliance Report.

  7. Click Context tab to configure settings.
  8. In File Path Regex, enter a valid Regex of the target file path to be monitored. Here are examples of file path Regex:
    1. ".*" targets all files in the cloud account.
    2. "^(?:[\w]\:|\\)(\\[a-z_\-\s0-9\.]+)+\.(txt|gif|pdf|doc|docx|xls|xlsx)$" targets files begin with x:\ or \\ with files ending in the following types of extensions: txt, gif, pdf, doc, docx, xls, xlsx. Here are the file paths that will this file path Regex matches:
      1. \\192.168.0.1\folder\file.pdf
      2. c:\my folder\abc abc.docx

    Reference:

    https://www.codeproject.com/Tips/216238/Regular-Expression-to-Validate-File-Path-and-Exten

  9. In Data Patterns, click on the field and select the data patterns (financial, personal identity information, etc.) to be monitored.
  10. Click Save to upgrade the configuration.

After the policy is enabled and configured, whenever any targeted sensitive file is accessed, an alert will be triggered in the alert page. For more details, please refer to Alert.

Compliance report will also record any alerts generated by this policy, for more details, please see Compliance Report.