POC: Data Mapping with Astralis
Our POC (Proof of Concept) guides are intended for enterprise organiations 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 AWS Data Mapping and Data Inventory
Please follow these guides, in order, for the appropriate environment to get started quickly with your Astralis POC (Proof of Concept):
In-House Systems
| Step | Description | Notes |
|---|---|---|
| AWS Provisioning | Provision AWS Credentials | AWS Guide to provisioning Access Key (opens in a new tab) |
| SQL Database Credential Provisioning | Provision a service account for Database Access | Astralis requires read-only permissions for classification. |
| Kubernetes Deployment (If Self-Deploying) | Access to deploy to AKS | AWS Guide to setting up Helm with EKS (opens in a new tab) |
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 Mapping
In-House Systems
| Step | Description | Notes |
|---|---|---|
| Astralis Scanning & Data Mapping | Scan the AWS Instance | Astralis guide to Detection & Discovery |
| Classify Sandbox AWS MySQL Database | Perform a classification and view results. | |
| Create a System in Astralis and link MySQL Dataset | Linking the dataset to a system. | Adding Data Uses and Processing Acitivites |
Third Party SaaS
| Step | Description | Notes |
|---|---|---|
| Integrate Third Party System | Astralis will use it's data dictionary to identify PII. | Example: Stripe - Configuring the integration |