Sentra
Purpose
Loads data security posture from Sentra: the data stores Sentra scans, the sensitive data classes found in each one, the policies that govern them, and active alerts. Each data store links to its AWS resource (S3 bucket, RDS instance or cluster, DynamoDB table, or Redshift cluster), and each alert becomes a security issue on the AWS resources it affects.
tip
Secret fields below accept either an AWS Secrets Manager ARN or a value pasted directly into Subimage's managed vault. See Secrets for details.
Required Fields
| Field | Secret? | Description |
|---|---|---|
sentra_api_key |
Yes | Sentra API key |
sentra_api_url |
No | (Optional) Sentra API base URL (default https://app.sentra.io) |
Setup Steps
- In Sentra, go to Settings → API Keys and generate an API key. Sentra shows the key only once, so copy it right away.
- Paste the key into Subimage's managed vault, or store it as a plaintext secret in AWS Secrets Manager and copy the Secret ARN.
- In Subimage, fill in
sentra_api_keyand save the module.
The key must be able to read these endpoints:
| Endpoint | Used for |
|---|---|
GET /api/core/users/current |
The Sentra organization the key belongs to |
POST /api/core/classes/search |
Data classes |
POST /api/core/data-stores/search |
Data stores |
POST /api/core/policies/search |
Policies |
POST /api/core/alerts/search |
Alerts |
GET /api/core/alerts/{alert_id}/violated_objects |
The data stores and data classes behind each alert |
Notes
- The sync is read-only.
- Links to AWS resources need the AWS module. Data stores and alerts whose resources are not in the graph yet link on the next Sentra sync after AWS has run.
- Only active alerts are loaded.
Troubleshooting
- Sentra Unauthorized: the key is wrong or was revoked. Generate a new one.
- Sentra Forbidden: the key cannot read one of the endpoints above.