Solution architecture outcome pattern: agent and its MCP servers
Some checks failed
check agents / check (push) Failing after 13s
Some checks failed
check agents / check (push) Failing after 13s
The cp1-solution-architecture-agent and the sa-aws/azure/gcp-cloud MCP servers, a separate stream from the individual and sub-agent patterns. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -0,0 +1,99 @@
|
||||
---
|
||||
name: aws-waf-security
|
||||
metadata:
|
||||
category: WellArchitectedFramework
|
||||
description: >-
|
||||
Generates security guidance for AWS workloads based on the Security pillar
|
||||
of the AWS Well-Architected Framework. Use when evaluating workloads,
|
||||
identifying security requirements, and recommending identity, detection,
|
||||
infrastructure, data and incident response controls.
|
||||
---
|
||||
|
||||
# AWS Well-Architected Framework skill for the Security pillar
|
||||
|
||||
## Overview
|
||||
|
||||
The Security pillar is the ability to protect data, systems and assets while
|
||||
taking advantage of cloud technologies. AWS organizes it into security
|
||||
foundations, identity and access management, detection, infrastructure
|
||||
protection, data protection, incident response and application security.
|
||||
|
||||
## Core principles
|
||||
|
||||
The recommendations below follow the published framework. Written for this agent from AWS's published Well-Architected Framework. Question codes are AWS's.
|
||||
|
||||
- **Implement a strong identity foundation**: Apply least privilege, separate
|
||||
duties, centralize identity, and avoid long-term credentials. Grounding
|
||||
document:
|
||||
https://docs.aws.amazon.com/wellarchitected/latest/framework/sec-design.html
|
||||
|
||||
- **Maintain traceability**: Monitor, alert and audit actions and changes in
|
||||
real time. Grounding document:
|
||||
https://docs.aws.amazon.com/wellarchitected/latest/framework/sec-design.html
|
||||
|
||||
- **Apply security at all layers**: Use defense in depth across the edge,
|
||||
network, compute, application and data. Grounding document:
|
||||
https://docs.aws.amazon.com/wellarchitected/latest/framework/sec-design.html
|
||||
|
||||
- **Automate security best practices**: Define controls as code in version
|
||||
control. Grounding document:
|
||||
https://docs.aws.amazon.com/wellarchitected/latest/framework/sec-design.html
|
||||
|
||||
- **Protect data in transit and at rest**: Classify data, and use encryption,
|
||||
tokenization and access control. Grounding document:
|
||||
https://docs.aws.amazon.com/wellarchitected/latest/framework/sec-design.html
|
||||
|
||||
- **Keep people away from data**: Reduce direct access and manual processing.
|
||||
Grounding document:
|
||||
https://docs.aws.amazon.com/wellarchitected/latest/framework/sec-design.html
|
||||
|
||||
- **Prepare for security events**: Have incident management in place, and run
|
||||
simulations. Grounding document:
|
||||
https://docs.aws.amazon.com/wellarchitected/latest/framework/sec-design.html
|
||||
|
||||
## Relevant products
|
||||
|
||||
The following are _examples_ of products relevant to this pillar:
|
||||
|
||||
- **Identity**: AWS IAM, AWS IAM Identity Center, AWS Organizations, service
|
||||
control policies
|
||||
- **Detection**: AWS CloudTrail, Amazon GuardDuty, AWS Security Hub, AWS Config
|
||||
- **Infrastructure**: Amazon VPC, security groups, AWS WAF, AWS Shield, AWS
|
||||
Network Firewall, AWS PrivateLink
|
||||
- **Data**: AWS KMS, AWS CloudHSM, AWS Secrets Manager, Amazon Macie, AWS
|
||||
Certificate Manager
|
||||
|
||||
## Workload assessment questions
|
||||
|
||||
Ask appropriate questions to understand the requirements and constraints of the
|
||||
workload and the organization. Choose from this list:
|
||||
|
||||
- SEC 1: How do you securely operate your workload?
|
||||
- SEC 2: How do you manage authentication for people and machines?
|
||||
- SEC 3: How do you manage permissions for people and machines?
|
||||
- SEC 4: How do you detect and investigate security events?
|
||||
- SEC 5: How do you protect your network resources?
|
||||
- SEC 6: How do you protect your compute resources?
|
||||
- SEC 7: How do you classify your data?
|
||||
- SEC 8: How do you protect your data at rest?
|
||||
- SEC 9: How do you protect your data in transit?
|
||||
- SEC 10: How do you anticipate, respond to, and recover from incidents?
|
||||
- SEC 11: How do you incorporate and validate the security properties of
|
||||
applications throughout the design, development, and deployment lifecycle?
|
||||
|
||||
## Validation checklist
|
||||
|
||||
Use this checklist to evaluate the architecture against this pillar:
|
||||
|
||||
- Accounts separate workloads and environments.
|
||||
- People use federated identity with MFA, and workloads use roles, not long-term
|
||||
keys.
|
||||
- Permissions follow least privilege, and service control policies set
|
||||
guardrails.
|
||||
- CloudTrail is on, and findings reach a named responder.
|
||||
- Network paths are restricted, with public exposure justified.
|
||||
- Compute is patched and hardened.
|
||||
- Data is classified, and encrypted at rest and in transit, with stated key
|
||||
ownership.
|
||||
- Secrets are held in Secrets Manager and rotated.
|
||||
- Incident response is planned and simulated.
|
||||
Reference in New Issue
Block a user