View a markdown version of this page

SEC10-BP01 Identify key personnel and external resources - AWS Well-Architected Framework

SEC10-BP01 Identify key personnel and external resources

Before an incident occurs, identify the internal responders, external partners, and legal contacts who investigate, communicate, and make decisions during a security event. Keep the list current so you can reach the right people quickly when one occurs.

Desired outcome:

  • You maintain a current list of key personnel with their roles, responsibilities, and at least two contact methods each.

  • Your list includes external parties such as software vendors, security partners, cloud providers, and the regulators you must notify.

  • Your responders have the context and access they need to act as soon as they are engaged.

  • You review and update the list on a schedule and after any organizational change.

  • You have an escalation path that engages a backup when a primary contact is unavailable.

Common anti-patterns:

  • Teams keep no current list of responders, so an event begins with a search for who to call.

  • Organizations assume all responders know the people, dependencies, and systems involved in a response.

  • Teams maintain no repository that describes key infrastructure or application design.

  • New employees join without onboarding that prepares them to contribute during an event.

  • Responders have no escalation path when a primary contact does not answer.

Benefits of establishing this best practice:

  • Responders engage faster because roles and contacts are known before an event.

  • Triage time drops because the right people arrive with context and access.

  • Communication with regulators, customers, and partners follows a known path.

  • Backups keep the response moving when a primary contact is unavailable.

  • New team members contribute sooner because onboarding includes response preparation.

Level of risk exposed if this best practice is not established: High

Implementation guidance

Consolidate your personnel and resource list in one system and update it as people join, change roles, or leave. Scattered contacts across wikis, chat histories, and personal notes slow down each response.

Define the response roles in advance.

  • An incident manager holds overall authority during a response and decides when to escalate.

  • Incident responders investigate and remediate. They are usually the developers and operators who own the affected workload, so the responders change with the type of event.

  • A communications lead handles internal updates and external notifications to customers, regulators, and public agencies.

  • For distributed teams, name a subject matter expert for each mission-critical workload who understands its operation and data classification.

Primary contacts are not always reachable. Escalate by role so a response continues when one person is unavailable. Give each contact at least two channels, as a single email address is a single point of failure. Use an on-call rotation to share the load and keep responders familiar with the workload.

Independent software vendors, managed service partners, and subcontractors may hold knowledge or access you need to recover. Arrange support relationships with them before an incident, including the appropriate level of Support for prompt access to AWS experts. Some events carry legal obligations. Publicly listed companies and regulated industries must notify agencies within defined windows, so keep contact details for the responsible departments current.

A dedicated incident management capability keeps contacts, on-call schedules, and escalation plans in one place and automates paging during an event. AWS Security Incident Response holds the team you want AWS to engage during a security event, with each member's title, email address, and notification preferences. Include leadership, legal counsel, managed detection and response partners, and the engineers who own the workload. The service does not schedule on-call rotations or page responders, so pair it with an incident management tool that does. Run this capability from your Security Tooling account so it stays available if a workload account is affected.

Implementation steps

  1. Set up an incident management solution: Choose a solution that stores contacts, on-call schedules, and escalation plans, and that pages whoever is on call. AWS Marketplace lists incident management solutions that handle on-call rotations, escalation, and automatic paging. Deploy it in your Security Tooling account so it stays available if a workload account is affected.

  2. Register your response team with AWS: Onboard AWS Security Incident Response and configure your incident response team. AWS can then engage the right people during a security event. Add the leadership, legal counsel, detection and response partners, and engineers who need to know, then set each member's notification preferences.

  3. Record contacts with multiple channels: Define each responder in your incident management solution with at least two contact channels, such as SMS, phone, and email. This redundancy keeps people reachable when one channel fails.

  4. Map roles to a contact directory: Document each person's role and responsibilities alongside their contacts, covering incident manager, incident responders, communications lead, and subject matter experts. Keep this directory current as people change roles or teams.

  5. Engage external partners and legal contacts: Establish support arrangements with your critical vendors and sign up for the Support plan that matches your response requirements. Record the agencies and regulators you must notify and the internal owners responsible for those notifications.

  6. Define a role-based response and escalation plan: Build a response plan that engages contacts by role rather than by name, with escalation paths for when a primary contact does not respond. Include contacts responsible for informing external entities even when they are not part of the technical response.

  7. Route alerts to responders automatically: Configure Amazon EventBridge rules to forward critical findings from AWS Security Hub CSPM or Amazon CloudWatch alarms to your incident management solution. The on-call responder is then paged without manual work. Have the same events open an operational work item in AWS Systems Manager OpsCenter, which is where you track the work a response generates. Each item carries a status, an owner, and the data about the affected resources. Responders can see what is still open and what is already done.

  8. Onboard and review on a cadence: Add new responders through an onboarding process that includes incident response simulations, and review the full contact list on a schedule and after each organizational change.

Resources

Related best practices:

Related documents:

Related videos:

Related examples:

Related tools: