SEC01: How do you securely operate your workload?
To operate your workload securely, you must apply overarching best practices to every area of security. Take requirements and processes that you have defined in operational excellence at an organizational and workload level, and apply them to all areas. Staying up to date with AWS and industry security threats and recommendations helps you evolve your threat model and control objectives. Automating security processes, testing, and validation allow you to scale your security operations.
Best Practices
This question includes the following best practices:
- SEC01-BP01: Separate workloads using accounts
- SEC01-BP02: Secure account root user and properties
- SEC01-BP03: Identify and validate control objectives
- SEC01-BP04: Stay up to date with security threats and recommendations
- SEC01-BP05: Reduce security management scope
- SEC01-BP06: Automate deployment of standard security controls
- SEC01-BP07: Identify threats and prioritize mitigations using a threat model
- SEC01-BP08: Evaluate and implement new security services and features regularly
Key Concepts
Security Operations Principles
Defense in Depth: Implement multiple layers of security controls throughout your workload. No single security control should be relied upon to protect your entire workload.
Shared Responsibility Model: Understand the division of security responsibilities between AWS and you as the customer. AWS secures the infrastructure, while you secure your workloads and data.
Continuous Security: Security is not a one-time implementation but an ongoing process that requires continuous monitoring, assessment, and improvement.
Foundational Security Elements
Account Separation: Use separate AWS accounts to isolate workloads and limit the blast radius of security incidents. This provides strong isolation boundaries and simplifies security management.
Root User Security: Protect the AWS account root user with the highest level of security controls, including MFA and restricted access.
Threat Modeling: Systematically identify potential threats to your workload and implement appropriate mitigations based on risk assessment.
Automation: Automate security processes wherever possible to reduce human error, ensure consistency, and scale security operations.
AWS Services to Consider
Implementation Approach
1. Foundation and Governance
- Establish multi-account architecture using AWS Organizations
- Secure root user accounts across all AWS accounts
- Implement baseline security controls and guardrails
- Define security policies and procedures
- Establish incident response procedures
2. Threat Assessment and Planning
- Conduct threat modeling exercises for your workloads
- Identify and document security control objectives
- Assess current security posture and identify gaps
- Prioritize security improvements based on risk
- Create security roadmap and implementation plan
3. Automation and Standardization
- Implement infrastructure as code for security controls
- Automate security assessments and compliance checks
- Standardize security configurations across environments
- Create reusable security templates and patterns
- Implement automated remediation where appropriate
4. Continuous Improvement
- Stay current with security threats and AWS security features
- Regularly review and update threat models
- Conduct security assessments and penetration testing
- Implement lessons learned from security incidents
- Continuously refine security processes and controls
Security Operations Framework
Preventive Controls
- Account Isolation: Separate workloads using AWS accounts
- Access Controls: Implement least privilege access principles
- Network Security: Control traffic flow and network access
- Data Protection: Encrypt data at rest and in transit
- Configuration Management: Maintain secure configurations
Detective Controls
- Logging and Monitoring: Comprehensive logging across all services
- Threat Detection: Real-time threat detection and alerting
- Compliance Monitoring: Continuous compliance assessment
- Vulnerability Management: Regular vulnerability scanning
- Security Metrics: Track security posture and trends
Responsive Controls
- Incident Response: Structured incident response procedures
- Automated Remediation: Automatic response to security events
- Forensic Capabilities: Tools and processes for investigation
- Recovery Procedures: Restore operations after incidents
- Communication Plans: Stakeholder communication during incidents
Common Challenges and Solutions
Challenge: Account Sprawl
Solution: Implement proper account governance with AWS Organizations, establish naming conventions, and use automation for account provisioning and management.
Challenge: Root User Management
Solution: Implement strong authentication for root users, limit root user usage to essential tasks only, and establish procedures for root user access.
Challenge: Security Control Consistency
Solution: Use infrastructure as code, implement automated deployment of security controls, and establish security baselines for all environments.
Challenge: Threat Model Maintenance
Solution: Establish regular threat modeling reviews, integrate threat modeling into development processes, and maintain threat intelligence feeds.
Challenge: Security Operations Scale
Solution: Implement automation for routine security tasks, use managed security services, and establish clear escalation procedures.
Security Maturity Levels
Level 1: Basic Security
- AWS account separation implemented
- Root user secured with MFA
- Basic logging enabled
- Manual security processes
Level 2: Managed Security
- Automated security control deployment
- Centralized security monitoring
- Regular security assessments
- Documented incident response procedures
Level 3: Optimized Security
- Continuous security monitoring and alerting
- Automated threat response
- Regular threat modeling updates
- Security metrics and continuous improvement
Level 4: Innovative Security
- Predictive security analytics
- AI/ML-powered threat detection
- Automated security orchestration
- Proactive threat hunting
Related resources
Table of contents
- SEC01-BP01 - Separate workloads using accounts
- SEC01-BP02 - Secure account root user and properties
- SEC01-BP03 - Identify and validate control objectives
- SEC01-BP04 - Stay up to date with security threats and recommendations
- SEC01-BP05 - Reduce security management scope
- SEC01-BP06 - Automate deployment of standard security controls
- SEC01-BP07 - Identify threats and prioritize mitigations using a threat model
- SEC01-BP08 - Evaluate and implement new security services and features regularly