Study guide
1.4 Amazon Macie & Automated Data Classification
AWS Certified Security – Specialty SCS-C03
Track your progress as you read
Finished sections get a check mark.
1 Chapter 0: Getting Started with the SCS-C03 Exam
0.1 SCS-C03 Exam Format, Domains & Study Strategy
2 Chapter 1: Security Monitoring, Alerting & Threat Detection Services
1.1 Workload Monitoring & Health Check Strategies 1.2 Amazon GuardDuty Architecture & Finding Types 1.3 AWS Security Hub & Automated Conformance Assessment 1.4 Amazon Macie & Automated Data Classification
3 Chapter 2: Enterprise Logging Architecture & Analysis
2.1 Multi-Account CloudTrail & Organization Trails 2.2 Amazon Security Lake & OCSF Log Normalization 2.3 Network Telemetry: VPC Flow Logs & Route 53 Resolver Logs 2.4 Troubleshooting Security Telemetry & Log Ingestion 2.5 Analyzing, Normalizing & Correlating Security Logs
4 Chapter 3: Incident Readiness, Response Planning & Automated Runbooks
3.1 Incident Response Planning & Blast Radius Mitigation 3.2 Testing & Validating Incident Response Plans 3.3 Automated Incident Remediation with EventBridge & Step Functions 3.4 Systems Manager OpsCenter & Incident Manager Runbooks
5 Chapter 4: Digital Forensics, Evidence Preservation & Root Cause Analysis
4.1 Forensic Artifact Capture & Chain of Custody 4.2 Threat Containment & Network Quarantine Techniques 4.3 Correlating Events & Root Cause Analysis with Amazon Detective
6 Chapter 5: Edge Protection, WAF & DDoS Mitigation
5.1 CloudFront Security Headers & Origin Access Control 5.2 AWS WAF Architecture & Advanced Rule Sets 5.3 AWS Shield Advanced & DDoS Defense Architectures 5.4 Edge Integrations: Managed Rule Groups, OCSF Ingestion, IoT Policies & CORS
7 Chapter 6: Compute Workload Hardening, Vulnerability Management & GenAI Security
6.1 Golden AMIs & Container Image Hardening Pipelines 6.2 Amazon Inspector Vulnerability Management & Patch Automation 6.3 Generative AI Security: Amazon Bedrock Guardrails & Model Protection 6.4 Instance Profiles, Service Roles & Execution Roles for Compute 6.5 Secure Administrative Access: Session Manager & EC2 Instance Connect
8 Chapter 7: Network Security, Segmentation, Private Connectivity & Encryption in Transit
7.1 Layered Traffic Filtering: SGs, NACLs & AWS Network Firewall 7.2 Hybrid Connectivity Security: VPN, Direct Connect & MACsec 7.3 Zero-Trust Access & Network Access Analysis 7.4 Enforcing Encryption in Transit: ELB Security Policies, TLS & HTTPS-Only Access 7.5 Private Access: VPC Endpoints, PrivateLink, Client VPN & Verified Access 7.6 Inter-Resource Encryption in Transit: Nitro, EMR, EKS & SageMaker AI
9 Chapter 8: Enterprise Authentication, Federation & Directory Services
8.1 AWS IAM Identity Center & Enterprise IdP Integration 8.2 Amazon Cognito User Pools & Identity Pools 8.3 AWS Security Token Service (STS) & Temporary Credential Workflows 8.4 Troubleshooting Identity & Authentication Failures
10 Chapter 9: Advanced Authorization Architecture & Policy Evaluation
9.1 Complete AWS Policy Evaluation Logic & Decision Flow 9.2 Permission Boundaries & Safe Admin Delegation 9.3 Attribute-Based Access Control (ABAC) with IAM Tags
11 Chapter 10: Least Privilege, Policy Validation & External Access Auditing
10.1 IAM Roles Anywhere & Amazon Verified Permissions 10.2 Auditing External & Unused Access with IAM Access Analyzer 10.3 Analyzing Authorization Failures & Policy Simulation
12 Chapter 11: Cryptographic Services: KMS Architecture & Key Governance
11.1 AWS KMS Architecture, Key Policies & Key Types 11.2 KMS Grants, Encryption Context & Multi-Region Keys 11.3 Imported Key Material (BYOK) & CloudHSM Key Stores
13 Chapter 12: Secrets Management, Sensitive Data Masking & PKI
12.1 AWS Secrets Manager & Systems Manager Parameter Store 12.2 Sensitive Data Masking in Telemetry & Messaging 12.3 AWS Certificate Manager (ACM) & Private CA Architecture
14 Chapter 13: Storage Encryption, Integrity, Lifecycle & Backup Protection
13.1 S3 Encryption Modes & S3 Bucket Keys 13.2 Data Integrity Protection: Object Lock, Vault Lock & Code Signing 13.3 Secure Data Lifecycle, Cross-Account Replication & Backup Vault Lock 13.4 Lifecycle, Backup & Secure Replication Beyond S3: EFS, FSx, DLM, DataSync & Air-Gapped Vaults
15 Chapter 14: Multi-Account Architecture, Organizations & Control Tower Governance
14.1 AWS Organizations Structure, Hierarchy & Resource Control 14.2 AWS Control Tower Landing Zone & Guardrail Framework 14.3 Delegated Administrator Architecture & Root User Governance 14.4 Centralized Resource Sharing with RAM & Service Catalog
16 Chapter 15: Compliance Automation, Infrastructure as Code Security & Auditing
15.1 Infrastructure as Code Security & Multi-Account Deployment 15.2 AWS Config, Conformance Packs & Automated Remediation 15.3 Audit Evidence Collection & Well-Architected Security Reviews
1.4 Amazon Macie & Automated Data Classification
Key Takeaways Explain This Topic AI
Amazon Macie provides automated discovery, classification, and privacy protection for sensitive data in Amazon S3, evaluating both bucket security posture and object-level content.
Automated sensitive data discovery continuously samples an organization's entire S3 bucket inventory to build interactive sensitivity heatmaps at minimal cost, while targeted classification jobs provide 100% deterministic inspection for compliance audits.
Managed Data Identifiers (MDIs) detect common sensitive formats (PII, credentials, financial records) out of the box, whereas Custom Data Identifiers (CDIs) use regex, proximity keywords, and ignore lists for proprietary enterprise data.
Macie emits two distinct finding categories: Policy Findings (evaluating bucket public access, encryption, and replication) and Sensitive Data Findings (identifying object content disclosures).
To inspect SSE-KMS encrypted objects, the Macie service-linked role must be explicitly granted kms:Decrypt permissions in the customer-managed key policy.
Last updated: September 2026
1.4 Amazon Macie & Automated Data Classification
Cloud data storage scalability makes Amazon S3 the primary repository for enterprise data lakes, application backups, and business analytics. However, decentralized storage frequently leads to shadow data , unencrypted personal information, exposed credentials, and accidental public disclosure. Amazon Macie is a specialized data security and privacy service that applies machine learning, pattern matching, and rule-based detectors to discover, classify, and protect sensitive data stored in Amazon S3.
Macie Architecture & Operational Objectives
Macie operates across two distinct operational domains within Amazon S3:
Bucket-Level Posture Evaluation : Continuously assesses security controls across all S3 buckets in an account or AWS Organization, evaluating public read/write access, default encryption settings, and cross-account or external replication permissions.
Object-Level Sensitive Data Classification : Inspects individual object contents to identify personally identifiable information (PII), payment card data, national identification numbers, healthcare records, and secret credentials.
Loading diagram...
Multi-Account Administration
In enterprise environments, Macie integrates with AWS Organizations . An AWS Organizations management account designates a dedicated security account as the Macie Delegated Administrator . The delegated administrator can:
Enable and configure Macie across all existing and newly created member accounts.
View aggregated bucket security posture and sensitive data heatmaps across the entire multi-account inventory.
Create and execute targeted sensitive data discovery jobs across member accounts.
Centrally deploy Custom Data Identifiers (CDIs) and suppression rules.
Continuous Automated Discovery vs Targeted Classification Jobs
Macie provides two operational models for content inspection, each tailored to distinct operational and budgetary requirements.
Operational Characteristic Automated Sensitive Data Discovery Targeted Sensitive Data Classification Jobs
Primary Purpose Continuous broad visibility; sensitivity heatmaps across entire S3 estate. In-depth deterministic verification for regulatory audits and compliance boundaries.
Inspection Scope Intelligent sampling of representative objects across all buckets. 100% comprehensive scanning of defined buckets, prefixes, and file types.
Cost Profile Predictable, cost-optimized sampling budget. Metered per gigabyte of uncompressed data scanned.
Configuration Overhead Zero-configuration; runs continuously once enabled. Requires defining job scope, schedule, sampling depth, and criteria.
Custom Identifiers Uses Macie's recommended managed identifiers by default; can be tailored with chosen managed identifiers, custom data identifiers , and allow lists. Uses managed identifiers, custom data identifiers (CDIs) , and allow lists chosen per job.
Audit Deliverable Interactive visual inventory & bucket sensitivity score (1–100, or −1 when Macie cannot analyze the bucket). Detailed finding reports, completion manifests, and sensitive data locations.
Automated Sensitive Data Discovery
When automated sensitive data discovery is activated, Macie continuously analyzes your S3 bucket inventory. It uses intelligent sampling algorithms to select small batches of objects across all buckets, inspecting them for sensitive data without scanning petabytes of redundant data. Macie calculates a sensitivity score for each bucket (1–100, with higher values meaning more sensitive data, or −1 when Macie can't analyze the objects) and assigns a matching sensitivity label. This highlights unknown shadow buckets containing unencrypted sensitive records.
Targeted Sensitive Data Classification Jobs
When legal or regulatory compliance mandates exhaustive proof that an S3 bucket is free of sensitive data (e.g., preparing a dataset for third-party machine learning training), security teams execute Targeted Classification Jobs :
Execution Frequency : Can be configured as a One-Time Job or a Scheduled Recurring Job (daily, weekly, or monthly) that evaluates only newly added or modified objects.
Scope Filtering : Allows granular inclusion/exclusion criteria based on S3 bucket name, object key prefix (folder path), object tag, file extension (e.g., .csv , .parquet , .json , .pdf ), file size (e.g., maximum 50 MB), and last modified timestamp.
Storage Class Support : Scans objects in S3 Standard, S3 Intelligent-Tiering, S3 Standard-IA, S3 One Zone-IA, and S3 Glacier Instant Retrieval. (Deep archive storage classes like Glacier Flexible and Deep Archive must be restored before Macie can inspect them).
Managed Data Identifiers vs Custom Data Identifiers
Macie inspects files using two classes of pattern recognition algorithms:
Managed Data Identifiers (MDIs)
Managed Data Identifiers are built-in detectors created and maintained by AWS. They incorporate regular expressions, checksum validation algorithms, and natural language context rules to identify standard sensitive data types:
Credentials : AWS secret access keys, private encryption keys (RSA/DSA/EC), GitHub personal access tokens, OpenSSH private keys, HTTP basic auth headers.
Financial Identifiers : Credit card numbers (validated against the Luhn checksum algorithm), international bank account numbers (IBAN), American Bankers Association (ABA) routing transit numbers.
Personal Identifiers (PII) : US Social Security Numbers (SSN), US driver's license numbers, passport numbers (US, UK, Canada, Germany, etc.), national identity numbers.
Healthcare Data : Health Insurance Claim Numbers (HICN), National Provider Identifiers (NPI).
Custom Data Identifiers (CDIs)
Many enterprises handle proprietary data that standard detectors cannot recognize, such as employee serial numbers, customer account formats, internal project codenames, or medical record numbers. Security engineers create Custom Data Identifiers (CDIs) to define proprietary detection rules.
A Custom Data Identifier combines one required pattern with optional refinements:
Regular Expression (Regex) : Defines the primary pattern match (up to 512 characters) (e.g., \b[A-Z]{3}-\d{6}-[A-Z]\b ).
Keywords (Proximity Matching) : Up to 50 keywords (3–90 characters each) that must precede the matched text within a maximum match distance of 1–300 characters (default 50). This dramatically reduces false positives. For example, if searching for an 8-digit customer ID, requiring proximity keywords like account , customer , cid , or client ensures random 8-digit transaction numbers are ignored.
Ignore Words : Up to 10 ignore words (4–90 characters each, case sensitive) that exclude a match (e.g., excluding test strings like EXAMPLE-ACCOUNT-00000000 ).
Occurrence-Based Severity : Optional thresholds that assign Low, Medium, or High severity according to how many matches an object contains. Without them, findings from a CDI are Medium.
Macie Finding Taxonomy: Policy vs Sensitive Data Findings
Macie generates two distinct categories of findings, both formatted in ASFF and published to EventBridge and Security Hub:
1. Policy Findings ( Policy:IAMUser/... )
Policy findings alert on S3 bucket-level permission and configuration vulnerabilities that expose data to risk:
Policy:IAMUser/S3BucketPublic : An S3 bucket permissions policy or access control list (ACL) allows public read or write access.
Policy:IAMUser/S3BucketSharedExternally : An S3 bucket is shared with an external AWS account outside your AWS Organization.
Policy:IAMUser/S3BucketReplicatedExternally : Bucket replication rules replicate data to a bucket in an external, unverified AWS account.
Policy:IAMUser/S3BucketEncryptionDisabled : An S3 bucket does not enforce default server-side encryption (SSE).
2. Sensitive Data Findings ( SensitiveData:S3Object/... )
Sensitive data findings indicate that a specific S3 object contains sensitive information:
SensitiveData:S3Object/Personal : Detected PII (names, SSNs, passports).
SensitiveData:S3Object/Financial : Detected credit cards, bank accounts, or financial transactions.
SensitiveData:S3Object/Credentials : Detected private keys, API tokens, or passwords.
SensitiveData:S3Object/CustomIdentifier : Detected matches against an active Custom Data Identifier.
Sensitive Data Sample Retrieval
By default, to maintain strict data privacy, Macie finding payloads include metadata (object ARN, bucket name, count of matches, identifier type) but do not display the raw sensitive data strings (e.g., the actual credit card digits). To allow security analysts to inspect the exact text that triggered the finding during investigation, an administrator can configure Sensitive Data Sample Retrieval :
Requires a configured repository (an S3 bucket) for sensitive data discovery results, because Macie uses those results to locate each occurrence.
Macie extracts the first 1–10 occurrences reported by the finding, up to 128 characters each, and encrypts them with an AWS KMS key that you specify .
Only principals allowed to call the reveal operation and use that key can see the samples, so restrict both with IAM policies and the key policy.
Specialty Exam Pitfalls & Data Protection Scenarios
KMS Key Policies and Macie Permissions : If an S3 bucket contains objects encrypted with AWS Key Management Service (SSE-KMS) using a customer-managed key (CMK), Macie cannot inspect those objects by default . The classification job will fail with an access denied error. To resolve this, you must update the KMS key policy to grant kms:Decrypt permissions to the Macie service-linked role ( arn:aws:iam::<account>:role/aws-service-role/macie.amazonaws.com/AWSServiceRoleForAmazonMacie ).
Unsupported Object Types : Macie cannot inspect encrypted files that have been client-side encrypted prior to upload if Macie does not possess the decryption key. Furthermore, Macie inspects common file formats (plain text, CSV, JSON, XML, Parquet, Avro, PDF, DOCX, XLSX, TAR, GZ, ZIP) but cannot execute binary database engines or inspect proprietary binary compiled files.
Policy Finding vs Sensitive Data Finding Remediation : Remediating a Policy finding (e.g., Policy:IAMUser/S3BucketPublic ) requires modifying bucket-level access controls, such as enabling S3 Block Public Access via the PutPublicAccessBlock API. Conversely, remediating a Sensitive Data finding requires object-level lifecycle actions: moving the object to an isolated quarantine bucket, applying stricter object ACLs, re-encrypting with a restricted KMS key, or triggering object deletion.
Sampling Is Not Proof of Absence : Automated sensitive data discovery can use custom data identifiers and allow lists, so it can watch an organization's buckets for a proprietary employee ID format. It still samples objects, however. When an auditor needs proof that every object in scope was inspected, run a targeted classification job instead.