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.
Your organization uses a proprietary internal identifier called Global-Logistics ID to track international shipments. These IDs follow a specific format (for example, GL-12345678) and are considered sensitive business information.
Your goal is to use this playbook to:
- Identify where these IDs are stored across your multi-cloud environment.
- Get notified when these IDs are found in unauthorized locations, such as public storage buckets or development accounts.
Relevant articles:
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:
- Go to Settings > Cloud Exposure > Data > Data Types, and click Add Custom Data Type.
-
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.
-
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.
- 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.
To create a custom data type for your shipping identifiers (comprised of the prefix "GL-" followed by 8 digits, such as GL-12345678), enter the following parameters into the Add Custom Data Type wizard:
- Name: Global-Logistics ID
- Description: Proprietary shipping identifier starting with the "GL-" prefix
- Category: PII
- Sensitivity: Private (Set to Private for the initial scan to avoid affecting the risk score. Update to Proprietary once validated)
Value and Context configurations:
- Include regex: \bGL-\d{8}\b
- Context regex: ShipmentID, LogisticsKey, Logistics
By adding the Context regex terms, you ensure that a random string of eight digits is not flagged unless it appears near a relevant logistics keyword.
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:
- 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.
-
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. - 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.
- If the samples match your expected data format, the detection signature is ready for policy enforcement.
After waiting for a scan cycle to complete, verify the accuracy of your new detection signature for the Global-Logistics ID.
- Discovery results — Navigate to the Data Resources page and filter by the Global-Logistics ID data type. The results show which resources contain this data type.. If the data type is located in unexpected resources, this might indicate that the regex should be more precise. Consider fine-tuning the Include regex.
- Check the location of the classified data — In the resource profile, go to Data > Classified Data, and find the object or table that contains the Global-Logistics ID data type. In that row, look at the Sample tooltip and verify the location of the sensitive data within the object or table.
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:
- Go to Policies > Cloud Policies and click Create Custom Policy.
- Enter the Name and Description.
- In the Type dropdown, select Template.
-
Click Select template.
-
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.
- 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.
- Under the Resources dropdown, select the relevant resource scope that would define the policy boundaries.
-
Select the Monitor Sensitive Data template and choose the governance strategy that fits your requirements with the relevant provider:
- 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.
- In the Remediation box, write your organization's workflow or steps that describe how to handle findings triggered by this policy.
Now that you have verified the Global-Logistics ID detection is accurate, you create a policy to ensure this data does not appear in public AWS buckets with the label Public.
- Custom policy configurations:
- Name: Global-Logistics ID Data Sprawl Monitoring
- Description: Global-Logistics ID not allowed in public buckets
- Template: Monitor Sensitive Data > AWS > This sensitive data should not reside in these resources
- Sensitive data > Sensitive data of these data types: Select the Global-Logistics ID data type.
- Resources > Data resources in these labels: Public.
- Severity: High (You choose High because any proprietary logistics ID in a public bucket is a direct violation of company policy).
-
Remediation:
Copy1. Block public access to the object
2. Open a Jira ticket and assign to InfoSec
Once saved, the system will now generate a finding the moment a Global-Logistics ID is detected in AWS public-facing buckets with the label Public.