Search for Well Architected Advice
-
Operational Excellence
-
- Resources have identified owners
- Processes and procedures have identified owners
- Operations activities have identified owners responsible for their performance
- Team members know what they are responsible for
- Mechanisms exist to identify responsibility and ownership
- Mechanisms exist to request additions, changes, and exceptions
- Responsibilities between teams are predefined or negotiated
-
- Executive Sponsorship
- Team members are empowered to take action when outcomes are at risk
- Escalation is encouraged
- Communications are timely, clear, and actionable
- Experimentation is encouraged
- Team members are encouraged to maintain and grow their skill sets
- Resource teams appropriately
- Diverse opinions are encouraged and sought within and across teams
-
- Use version control
- Test and validate changes
- Use configuration management systems
- Use build and deployment management systems
- Perform patch management
- Implement practices to improve code quality
- Share design standards
- Use multiple environments
- Make frequent, small, reversible changes
- Fully automate integration and deployment
-
- Have a process for continuous improvement
- Perform post-incident analysis
- Implement feedback loops
- Perform knowledge management
- Define drivers for improvement
- Validate insights
- Perform operations metrics reviews
- Document and share lessons learned
- Allocate time to make improvements
- Perform post-incident analysis
-
Security
-
- Separate workloads using accounts
- Secure account root user and properties
- Identify and validate control objectives
- Keep up-to-date with security recommendations
- Keep up-to-date with security threats
- Identify and prioritize risks using a threat model
- Automate testing and validation of security controls in pipelines
- Evaluate and implement new security services and features regularly
-
- Define access requirements
- Grant least privilege access
- Define permission guardrails for your organization
- Manage access based on life cycle
- Establish emergency access process
- Share resources securely within your organization
- Reduce permissions continuously
- Share resources securely with a third party
- Analyze public and cross-account access
-
- Perform regular penetration testing
- Deploy software programmatically
- Regularly assess security properties of the pipelines
- Train for Application Security
- Automate testing throughout the development and release lifecycle
- Manual Code Reviews
- Centralize services for packages and dependencies
- Build a program that embeds security ownership in workload teams
-
-
Reliability
-
- Be aware of service quotas and constraints in Cloud Services
- Manage service quotas across accounts and Regions
- Accommodate fixed service quotas and constraints through architecture
- Monitor and manage quotas
- Automate quota management
- Ensure sufficient gap between quotas and usage to accommodate failover
-
- Use highly available network connectivity for your workload public endpoints
- Provision Redundant Connectivity Between Private Networks in the Cloud and On-Premises Environments
- Ensure IP subnet allocation accounts for expansion and availability
- Prefer hub-and-spoke topologies over many-to-many mesh
- Enforce non-overlapping private IP address ranges in all private address spaces where they are connected
-
- Monitor end-to-end tracing of requests through your system
- Conduct reviews regularly
- Analytics
- Automate responses (Real-time processing and alarming)
- Send notifications (Real-time processing and alarming)
- Define and calculate metrics (Aggregation)
- Monitor End-to-End Tracing of Requests Through Your System
- Define and calculate metrics
- Send notifications
- Automate responses
-
- Monitor all components of the workload to detect failures
- Fail over to healthy resources
- Automate healing on all layers
- Rely on the data plane and not the control plane during recovery
- Use static stability to prevent bimodal behavior
- Send notifications when events impact availability
- Architect your product to meet availability targets and uptime service level agreements (SLAs)
-
-
Cost Optimization
-
- Establish ownership of cost optimization
- Establish a partnership between finance and technology
- Establish cloud budgets and forecasts
- Implement cost awareness in your organizational processes
- Monitor cost proactively
- Keep up-to-date with new service releases
- Quantify business value from cost optimization
- Report and notify on cost optimization
- Create a cost-aware culture
-
- Perform cost analysis for different usage over time
- Analyze all components of this workload
- Perform a thorough analysis of each component
- Select components of this workload to optimize cost in line with organization priorities
- Perform cost analysis for different usage over time
- Select software with cost effective licensing
-
-
Performance
-
- Learn about and understand available cloud services and features
- Evaluate how trade-offs impact customers and architecture efficiency
- Use guidance from your cloud provider or an appropriate partner to learn about architecture patterns and best practices
- Factor cost into architectural decisions
- Use policies and reference architectures
- Use benchmarking to drive architectural decisions
- Use a data-driven approach for architectural choices
-
- Use purpose-built data store that best support your data access and storage requirements
- Collect and record data store performance metrics
- Evaluate available configuration options for data store
- Implement Strategies to Improve Query Performance in Data Store
- Implement data access patterns that utilize caching
-
- Understand how networking impacts performance
- Evaluate available networking features
- Choose appropriate dedicated connectivity or VPN for your workload
- Use load balancing to distribute traffic across multiple resources
- Choose network protocols to improve performance
- Choose your workload's location based on network requirements
- Optimize network configuration based on metrics
-
- Establish key performance indicators (KPIs) to measure workload health and performance
- Use monitoring solutions to understand the areas where performance is most critical
- Define a process to improve workload performance
- Review metrics at regular intervals
- Load test your workload
- Use automation to proactively remediate performance-related issues
- Keep your workload and services up-to-date
-
-
Sustainability
-
- Scale workload infrastructure dynamically
- Align SLAs with sustainability goals
- Optimize geographic placement of workloads based on their networking requirements
- Stop the creation and maintenance of unused assets
- Optimize team member resources for activities performed
- Implement buffering or throttling to flatten the demand curve
-
- Optimize software and architecture for asynchronous and scheduled jobs
- Remove or refactor workload components with low or no use
- Optimize areas of code that consume the most time or resources
- Optimize impact on devices and equipment
- Use software patterns and architectures that best support data access and storage patterns
- Remove unneeded or redundant data
- Use technologies that support data access and storage patterns
- Use policies to manage the lifecycle of your datasets
- Use shared file systems or storage to access common data
- Back up data only when difficult to recreate
- Use elasticity and automation to expand block storage or file system
- Minimize data movement across networks
- Implement a data classification policy
- Remove unneeded or redundant data
-
- Articles coming soon
< All Topics
Print
Automate testing throughout the development and release lifecycle
PostedNovember 29, 2024
UpdatedMarch 21, 2025
ByKevin McCaffrey
Automating testing for security properties at every stage of the development and release lifecycle is crucial. By ensuring consistent and repeatable testing, teams can identify potential vulnerabilities early on, which significantly reduces security risks in final deployments.
Best Practices
Implement Continuous Security Testing
- Integrate security testing tools into your CI/CD pipeline to automatically assess security properties during code integration and deployment.
- Utilize static application security testing (SAST) tools to analyze source code for vulnerabilities early in the development process.
- Employ dynamic application security testing (DAST) to evaluate running applications for security weaknesses before production release.
- Conduct regular security assessments, including penetration testing, to identify and remediate vulnerabilities.
- Incorporate security training for development teams to ensure they are aware of best practices and common security pitfalls.
Questions to ask your team
- What security testing frameworks are you using in your development lifecycle?
- How do you ensure that security tests are automated and integrated into your CI/CD pipelines?
- What tools are you leveraging for static and dynamic application security testing?
- How frequently are your security tests run, and how are results tracked and addressed?
- Do you have a process for evaluating and updating your automation testing strategy as new vulnerabilities are discovered?
Who should be doing this?
Security Engineer
- Design security measures and frameworks to integrate into the development lifecycle.
- Identify security requirements and risks associated with applications.
- Develop and maintain automation scripts for security testing.
DevOps Engineer
- Implement CI/CD pipelines that include automated security testing.
- Manage the integration of security tools within the deployment process.
- Monitor and audit automated security test results and compliance.
Software Developer
- Write code that adheres to security best practices and guidelines.
- Collaborate with security teams to ensure the application meets security requirements.
- Address vulnerabilities identified during automated security tests.
Quality Assurance (QA) Engineer
- Develop test cases that include security testing elements.
- Execute automated security tests and report findings.
- Ensure that security testing is incorporated into the overall quality assurance process.
Project Manager
- Coordinate security testing activities throughout the project lifecycle.
- Ensure resources and training are available for team members regarding security practices.
- Monitor the progress of security integration and communicate risks to stakeholders.
What evidence shows this is happening in your organization?
- Security Testing Automation Plan: A comprehensive plan detailing the integration of automated security testing tools in the CI/CD pipeline, including specific tools, scheduling, and environment setup.
- Automated Security Testing Checklist: A checklist that outlines the essential security tests to be automated at each stage of the development lifecycle, ensuring coverage of common vulnerabilities and compliance requirements.
- Security Testing Dashboard: An interactive dashboard that visualizes the results of automated security tests including trends over time, identified vulnerabilities, and remediation status.
- Policy on Security Testing Practices: A formal policy document that outlines the organization’s commitment to security testing, roles and responsibilities, testing standards, and adherence to compliance.
- Security Testing Strategy Guide: A strategic guide outlining the goals, methodologies, and tools for implementing effective automated security testing across all development and deployment stages.
Cloud Services
AWS
- AWS CodePipeline: Automates the building, testing, and deployment of applications, allowing for integration of security testing in the CI/CD pipeline.
- Amazon Inspector: Automatically assesses applications for vulnerabilities and security best practices, providing valuable insights during the development lifecycle.
- AWS Security Hub: Aggregates security findings from multiple AWS services, providing a comprehensive overview of security posture and compliance throughout application lifecycles.
Azure
- Azure DevOps: Provides CI/CD tools to automate testing and deployment, integrating security testing at every phase of application development.
- Azure Security Center: Continuously monitors your Azure resources to identify security vulnerabilities and recommends mitigations, supporting secure development practices.
- Azure Active Directory (AD): Enables secure identity management and access control, helping to assert security measures throughout the application lifecycle.
Google Cloud Platform
- Cloud Build: Automates the CI/CD process, allowing for the integration of security testing as part of the build and deployment process.
- Container Analysis: Provides vulnerability scanning for container images, ensuring that security is addressed early in the development process.
- Google Cloud Security Command Center: Offers risk assessment and security posture management tools for all Google Cloud services, helping secure applications in development.
Question: How do you incorporate and validate the security properties of applications throughout the design, development, and deployment lifecycle?
Pillar: Security (Code: SEC)
Table of Contents