Governing Proprietary Sensitive Data

Objective

Identify, monitor, and secure data specific to your business to prevent data sprawl into unsecured locations. By creating custom data types and adding them to custom policies, you can track unique data patterns and receive alerts when they are discovered outside of authorized boundaries.

If you have information specific to your business, such as internal account IDs or project codes, it may not be covered by Tenable One Cloud Exposure built-in data types. This playbook provides the workflow to ensure sensitive information remains within secure environments and triggers alerts if it is moved to unauthorized locations.

Relevant articles:

Note: Playbooks serve as blueprints for operationalizing security workflows within the platform. The steps outlined show a repeatable methodology for transforming technical visibility into a consistent, actionable outcome. While this guide focuses on a specific use case, these principles can be applied to other resource types and security scenarios to ensure comprehensive risk management across your environment.

Step 1: Define Your Business-Specific Data (Custom Data Types)

To govern data that is unique to your organization, you first need to define its structure as a custom data type so Cloud Exposure can recognize it. Whether it’s a specific employee ID format or a customer loyalty number, a precise definition is the foundation for high-accuracy scanning and reliable discovery.

To create a custom data type:

  1. Go to Settings > Cloud Exposure > Data > Data Types, and click Add Custom Data Type.
  2. Define the data type parameters, including its Name, Category, and Sensitivity.
    • It is recommended to set the Sensitivity to Public or Private for the initial scan. This allows you to observe discovery results and verify detection accuracy without immediately triggering high-severity alerts or impacting the risk score of resources.
  3. Define the unique structure of your data in the Include regex fields using the RE2 format.
    • It is recommended to use a tool such as regex101.com to ensure the pattern is accurate.
    • For example, a Global-Logistics ID composed of the prefix "GL-" followed by 8 digits ("GL-12345678") would require the expression \bGL-\d{8}\b.
  4. You can add Context keywords to increase detection accuracy. These keywords ensure Cloud Exposure only flags a match when your regex appears in proximity to relevant terms in unstructured files, or aligns with specific column names and JSON keys in structured data.

Step 2: Validate Discovery and Accuracy

A policy is only as effective as the detection logic behind it. Before you create policies, you must confirm that your detection logic works as intended. This phase ensures that your regex and context keywords identify the correct information.

To validate your discovery:

  1. Allow Cloud Exposure to complete a scan cycle. It typically takes 24 to 48 hours for discovery results to populate in the Console after creating a new data type or updating an existing data type.
  2. Navigate to Explore > Data Resources and filter the inventory by your new Data Type to isolate the specific resources that triggered a match.

    Important: If you see zero results or if the data type is located in unexpected resources, this might indicate that the regex should be more precise. Consider going back to Step 1 to refine your Include or Context regex.
  3. In the resource, go to Data > Classified Data, and find the object or table that contains the data type. Use the Sample tooltip to verify the location of the sensitive data within the object or table.
  4. If the samples match your expected data format, the detection signature is ready for policy enforcement.
Note: After the initial scan is complete and you have verified the results, update the sensitivity level of the data type to Proprietary.

Step 3: Enforce Governance (Custom Cloud Policies)

Once you have verified your detection logic, you can move from discovery to active governance by creating custom policies. This step allows you to monitor data sprawl by determining where your proprietary data is permitted to reside and triggers alerts when it moves outside of those boundaries.

To create a custom policy:

  1. Go to Policies > Cloud Policies and click Create Custom Policy.
  2. Enter the Name and Description.
  3. In the Type dropdown, select Template.
  4. Click Select template.
    1. Select the Monitor Sensitive Data template and choose the governance strategy that fits your requirements with the relevant provider:
      • This sensitive data should not reside in these resources: A finding is generated when sensitive data appears in unauthorized locations, such as public-facing storage or development environments.
      • This sensitive data should reside only in these resources: Ensure that your sensitive data only resides within approved resources. A finding is generated when the data is discovered outside of the defined boundary.
    2. Under the Sensitive data dropdown, select the sensitive data you want to monitor. Specifically, select the relevant data type from the Sensitive data of these data types option.
    3. Under the Resources dropdown, select the relevant resource scope that would define the policy boundaries.
  5. Set the Severity level of the findings generated from this policy. This determines how these findings are prioritized and displayed within your environment based on your internal risk management standards.
  6. In the Remediation box, write your organization's workflow or steps that describe how to handle findings triggered by this policy.