AWS security for a corporation: which account each service lives in

AWS offers more than forty security services. The official list groups them into categories (identity, detection, infrastructure, data, incident response and compliance), and that list tells you what exists. It does not tell you where each one goes. In a company with dozens of accounts, that is the question that matters: which account each service is managed from, and who can touch it.
How to read the map
The map below places each service in the account it is normally managed from inside a multi-account organization. Each account exists to separate one responsibility, and the color shows the service's category.
Map: where each AWS security service lives
Pick a category to highlight the accounts it is managed from. Everything runs in your browser: nothing is sent.
Corporation
Organization management account
It only governs: it creates accounts, applies policies and pays. No workload runs here.
- Identity and access: AWS OrganizationsOUs, SCPs and resource policies
- Identity and access: AWS Control TowerLanding zone and preventive controls
- Identity and access: IAM Identity CenterSingle sign-on with MFA to every account
- Detective controls: AWS CloudTrailOrganization trail; accounts cannot turn it off
- Detective controls: AWS Trusted AdvisorBest-practice checks across the organization
- Data protection: S3 Block Public AccessEnforced block for the whole organization
- Incident response: AWS BackupBackup policies inherited by OU
- Compliance: AWS ArtifactAWS compliance reports (SOC, ISO, PCI)
Security
Security Tooling account
Delegated administrator for the security services. The security team sees everything from here.
- Detective controls: AWS Security HubFindings from every account and region
- Detective controls: Amazon GuardDutyThreat detection, delegated administrator
- Detective controls: AWS ConfigAggregator: inventory and conformance
- Infrastructure security: Amazon InspectorVulnerabilities in EC2, images and Lambda
- Data protection: Amazon MacieSensitive data in S3
- Identity and access: IAM Access AnalyzerExternal access and unused permissions
- Infrastructure security: AWS Firewall ManagerWAF, Shield and firewall rules for every account
- Incident response: AWS Config RulesDetect drift and trigger the fix
- Supporting: Amazon EventBridgeRoutes each finding to its response
- Incident response: AWS LambdaTargeted automatic remediation
- Incident response: AWS Step FunctionsMulti-step playbooks with approval
- Incident response: SSM AutomationRunbooks: isolate, snapshot, patch
- Incident response: Amazon DetectiveRoot-cause investigation
- Compliance: AWS Audit ManagerContinuous evidence collection
- Data protection: AWS KMSKeys to encrypt findings and evidence
Log Archive account
Immutable log archive. Almost nobody gets in and nobody deletes.
- Detective controls: Amazon Security LakeLogs normalized to OCSF; feeds the SIEM
- Supporting: Amazon S3Central bucket with Object Lock and retention
- Data protection: Server-Side EncryptionLogs encrypted at rest with KMS
- Detective controls: AWS CloudTrailDestination of the organization trail
- Detective controls: VPC Flow LogsDestination of network logs from every VPC
- Detective controls: Amazon CloudWatchCross-account centralized logs and metrics
Infrastructure
Network account
Owns the perimeter: everything entering or leaving the Internet goes through here.
- Infrastructure security: AWS ShieldDDoS protection
- Infrastructure security: AWS WAFLayer 7 filtering and bot control
- Supporting: Amazon CloudFrontEdge delivery; produces access logs
- Data protection: AWS Certificate ManagerPublic TLS certificates
- Identity and access: AWS Verified AccessAccess to internal applications without a VPN
- Infrastructure security: Amazon VPCSubnets, route tables, NAT and endpoints
- Detective controls: VPC Flow LogsA record of every accepted or rejected connection
- Infrastructure security: AWS Network FirewallStateful inspection, IDS and IPS
- Detective controls: Traffic MirroringTraffic copy for deep analysis
Shared Services account
Services every account consumes and nobody should duplicate.
- Identity and access: AWS Directory ServiceCorporate directory, the source of identities
- Infrastructure security: AWS Systems ManagerInventory, patching and access without SSH
- Infrastructure security: EC2 Image BuilderHardened images shared with the workloads
- Incident response: AWS BackupCentral vault with cross-account copies
Workloads
Application account (one per system and environment)
Where the business runs. The product team operates here, within the limits the organization sets.
- Identity and access: Amazon CognitoCustomer sign-up and sign-in
- Identity and access: Amazon Verified PermissionsFine-grained authorization inside the application
- Identity and access: AWS Secrets ManagerCredentials with automatic rotation
- Identity and access: AWS IAMOne role per function, task or service
- Infrastructure security: Amazon VPCPrivate subnets, security groups and endpoints
- Infrastructure security: AWS Systems ManagerAgent: patching and sessions with no open ports
- Infrastructure security: Amazon InspectorContinuous scanning of the instances
- Detective controls: VPC Flow LogsSent to Log Archive
- Data protection: AWS KMSDedicated keys per system or per customer
- Data protection: Server-Side EncryptionS3, EBS and databases encrypted by default
- Data protection: AWS CloudHSMWhen the regulation requires a dedicated HSM
- Data protection: AWS Payment CryptographyPayment operations under PCI
- Data protection: AWS Certificate ManagerInternal TLS and private CA
Recovery account
An isolated copy that survives a deletion or ransomware in the application account.
- Incident response: AWS Elastic Disaster RecoveryContinuous server replication to another region
- Incident response: AWS BackupLocked vault, logically separated
- Data protection: AWS KMSKeys different from production
- Identity and access: AWS IAMRoles, no long-lived keys
- Detective controls: AWS CloudTrailOrganization trail
- Detective controls: AWS ConfigConfiguration recorder
- Detective controls: Amazon GuardDutyThreat detection member account
- Detective controls: AWS Security HubFindings member account
- Identity and access: IAM Access AnalyzerAccount analyzer
- Detective controls: Amazon CloudWatchAlarms and logs
- Supporting: Amazon EventBridgeEvent forwarding to security
Four paths worth being able to explain
Logs: from every account to the central archive
- CloudTrail, VPC Flow Logs, DNS and WAF
- S3 in Log Archive
- Security Lake (OCSF)
- SIEM or Athena
Nobody in the workload accounts can delete or alter the log, because it lives in another account with Object Lock.
Findings: from detection to remediation
- GuardDuty, Inspector, Macie, Config Rules
- Security Hub
- EventBridge
- Lambda, Step Functions or SSM Automation
Everything converges in Security Tooling. Detective is for investigating the cause before or after containment.
People access: no permanent IAM users
- Corporate directory
- IAM Identity Center
- Temporary role in the account
- SCP boundary
The effective permission is the intersection of the permission set and what the OU's SCP lets through.
Inbound traffic: inspection before the application
- Shield and CloudFront
- WAF
- Inbound VPC
- Network Firewall
- Application VPC
The network account owns the perimeter; application accounts have no Internet egress of their own.
Study diagram based on the public pattern of the AWS multi-account security reference architecture. Each service is shown in its most common location; several are managed from a delegated account and operate in all of them. Services marked as supporting are not security services, but they complete the path.