AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb navigation and simplified AWS service names (removed 'Amazon'/'AWS' prefixes from GuardDuty, Security Hub, Audit Manager, Detective)
Security assessment
Changes are cosmetic/naming improvements without altering security guidance. The security recommendations for dedicated accounts remain identical. Simplified service names don't impact security posture or introduce new security features.
Diff
diff --git a/prescriptive-guidance/latest/security-reference-architecture/dedicated-accounts.md b/prescriptive-guidance/latest/security-reference-architecture/dedicated-accounts.md index 617d18f49..7f619c7eb 100644 --- a//prescriptive-guidance/latest/security-reference-architecture/dedicated-accounts.md +++ b//prescriptive-guidance/latest/security-reference-architecture/dedicated-accounts.md @@ -3 +3 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[AWS Security Reference Architecture](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[AWS Security Reference Architecture (AWS SRA) – core architecture](introduction.html) @@ -12 +12 @@ An AWS account provides security, access, and billing boundaries for your AWS re -When designing your OU and account structure, start with security and infrastructure in mind. We recommend creating a set of foundational OUs for these specific functions, split into Infrastructure and Security OUs. These OU and account recommendations capture a subset of our broader, more comprehensive guidelines for AWS Organizations and multi-account structure design. For a full set of recommendations, see [Organizing Your AWS Environment Using Multiple Accounts](https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/organizing-your-aws-environment.html) in the AWS documentation and the blog post [Best Practices for Organizational Units with AWS Organizations](https://aws.amazon.com/blogs/mt/best-practices-for-organizational-units-with-aws-organizations/). +When designing your OU and account structure, start with security and infrastructure in mind. We recommend creating a set of foundational OUs for these specific functions, split into Infrastructure and Security OUs. These OU and account recommendations capture a subset of our broader, more comprehensive guidelines for AWS Organizations and multi-account structure design. For a full set of recommendations, see [Organizing your AWS environment using multiple accounts](https://docs.aws.amazon.com/whitepapers/latest/organizing-your-aws-environment/organizing-your-aws-environment.html) in the AWS documentation and the blog post [Best practices for organizational units with AWS Organizations](https://aws.amazon.com/blogs/mt/best-practices-for-organizational-units-with-aws-organizations/). @@ -19 +19 @@ Management | — | Central governance and management of all AWS Regions and acco -Security Tooling | Security | Dedicated AWS accounts for operating broadly applicable security services (such as Amazon GuardDuty, AWS Security Hub CSPM, AWS Audit Manager, Amazon Detective, Amazon Inspector, and AWS Config), monitoring AWS accounts, and automating security alerting and response. (In AWS Control Tower, the default name for the account under the Security OU is _Audit account_.) +Security Tooling | Security | Dedicated AWS accounts for operating broadly applicable security services (such as GuardDuty, Security Hub CSPM, Audit Manager, Detective, Amazon Inspector, and AWS Config), monitoring AWS accounts, and automating security alerting and response. (In AWS Control Tower, the default name for the account under the Security OU is _Audit account_.)