feat(ontology): add Secret semantic label for cross-platform secret queries #2349
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Summary
This PR adds a new
secretscategory to the Cartography ontology, enabling unified cross-platform querying of secrets and credentials across multiple cloud providers.Supported providers:
SecretsManagerSecret)GCPSecretManagerSecret)AzureKeyVaultSecret)GitHubActionsSecret- org, repo, and env levels)KubernetesSecret)Normalized ontology fields:
_ont_name_ont_created_at_ont_updated_at_ont_rotation_enabledThis enables queries like:
Related issues or links
How was this tested?
make test_lint)ExtraNodeLabels(["Secret"])is correctly set on all 7 schema classesChecklist
General
make lint).Proof of functionality
If you are changing a node or relationship
Notes for reviewers
SecretsManagerSecretVersion, GCPGCPSecretManagerSecretVersion) are intentionally excluded as they are child entitiesSecretlabel follows the same semantic label pattern asAPIKey,Database,Function, etc.