This whitepaper is for historical reference only. Some content might be outdated and some links might not be available.
Discovering and Protecting Data at Scale with Amazon Macie
Article 32 of the GDPR states that “…the controller and the processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk, including inter alia as appropriate: […]
(b) the ability to ensure the ongoing confidentiality, integrity, availability and resilience of processing systems and services;
[…]
(d) a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.”
Having an ongoing data classification process is critical for adjusting security data
processing to the nature of data. If your organization manages sensitive data, monitor where
it resides, protect it properly, and provide evidence that you are enforcing data security and
privacy as required to meet regulatory compliance requirements. To help the customer identify
and protect their sensitive data at scale, AWS offers Amazon Macie,
Amazon Macie continually evaluates the object inside the buckets and automatically
provides a summary of findings (Figure 4) for any unencrypted or publicly accessible data
discovered that match with the defined data category. This data can include alerts for any
unencrypted, publicly accessible objects or buckets shared with AWS accounts outside those you
have defined in AWS Organizations. Amazon Macie is integrated with other AWS services, such as
AWS Security Hub

Figure 4 – Data inspections and finding example
In order to prevent sensitive data accidental disclosure, coming from log data in-transit such as credit card numbers or government ID’s logged by your systems, and applications, Amazon CloudWatch provides data protection account level policy. Account level policies work in combination with log group level policies, allowing you to select patterns of sensitive log data to detect and protect broadly across all log groups in an AWS account. By default, when a user views a log event that includes masked data, the sensitive data is replaced by asterisks according to the policy.