POC: Data Subject Requests within Astralis
Our POC (Proof of Concept) guides are intended for enterprise organizations evaluating Astralis deployed in their environment and are a helpful way to guide you through deploying and evaluating the world's leading privacy engineering platform.
Prerequisites Guide for Data Subject Requests (DSRs).
Please follow these guides, in order, for the appropriate environment to get started quickly with your Astralis POC (Proof of Concept):
Astralis Deployment
| Step | Description | Notes |
|---|---|---|
| Deploy Astralis Server | Deploy the Astralis Core server for Data Governance | Deploying and Configuring Astralis |
| Deploy Privacy Center | This allows you to simulate end-user flows. | Deploying and Configuring the Privacy Center |
| (Optional) S3 Bucket Configuration | Configure an S3 bucket as a destination for DSR packages. (requires AWS Access Key) | Astralis can use an S3 bucket to output the DSR package: 1. AWS Guide to provisioning Access Key (opens in a new tab) 2. Configuring Storage Destinations |
SQL Database
| Step | Description | Notes |
|---|---|---|
| SQL Database Credential Provisioning | Provision a service account for Database Access | Astralis requires read and write access to modify the database. |
| SQL Database Network Connectivity | Astralis will need to have network connectivity from the Admin Server, (Optional) Worker nodes, to the database. | For a POC, we recommend basic connectivity, however for a production deployment please refer to our security best practices |
Third Party SaaS
| Step | Description | Notes |
|---|---|---|
| Credential Provisioning | Provision Access Keys for third party systems | Refer to vendor documentation for seeding third party system data |
| Seed Test Data | Evaluator will provision sandbox data in a non-production environment | Example: Stripe - Generating test data (opens in a new tab) |
POC Checklist for Data Subject Requests
SQL Database
| Step | Description | Notes |
|---|---|---|
| Generate a Dataset | Create a Dataset for your SQL database for Astralis to traverse and generate a DSR. | Generate Dataset |
| Annotate Dataset | Download and annotate the dataset with data_categories and an identity key.Note - if you use the Astralis Classifier, this is done for you automatically. Alternatively you can download the file and use the Astralis CLI tooling or use the {{FIDES_SERVER_URL}}:8080/docs endpoint where you can view the Swagger docs and make a request via the API. | Annotating a Dataset Adding Identity key |
| (Optional) Define Database Relationships | Define the entity relationships within your database with additional annotations. You can also use dbml-to-fides (opens in a new tab) to do this. These annotations ensure that Astralis can correctly traverse all tables and relationships during a privacy request. | Annotate Relationships dbml-to-fides (opens in a new tab) |
| Link the Dataset | Connect the dataset to the System to enable privacy requests against your database. | Link Datasets |
| Test your integration | Test your request via the Astralis Privacy Center or DSR client, and approve it in the Astralis administrative console. | Submitting a Request Approving a Request |
Third Party SaaS
| Step | Description | Notes |
|---|---|---|
| Integrate Third Party System | Astralis comes pre-configured with SaaS connectors that integrate into third party systems. | Example: Stripe - Configuring the integration |
| Test your integration | Test your request via the Astralis Privacy Center or DSR client, and approve it in the Astralis administrative console. | Submitting a Request Approving a Request |