AWS security-ir documentation change
Summary
Replaced 'AWS SIRT' with 'Security Incident Response Engineering' in SIEM and MDR integration descriptions.
Security assessment
Cosmetic naming update without altering security processes or addressing vulnerabilities. No evidence of security incident remediation.
Diff
diff --git a/security-ir/latest/userguide/integrate-existing-tools.md b/security-ir/latest/userguide/integrate-existing-tools.md index dc2d48325..12b6bd138 100644 --- a//security-ir/latest/userguide/integrate-existing-tools.md +++ b//security-ir/latest/userguide/integrate-existing-tools.md @@ -96 +96 @@ For deployment instructions, see [AWS sample solutions for Jira, Slack, and Serv -AWS Security Incident Response doesn't directly ingest findings from your SIEM. However, when you open an AWS-supported case, AWS SIRT responders analyze and investigate SIEM findings in parallel with your team. SIRT helps identify correlations across hybrid and multi-cloud environments and assists with scoping threat actor activity across providers. +AWS Security Incident Response doesn't directly ingest findings from your SIEM. However, when you open an AWS-supported case, Security Incident Response Engineering responders analyze and investigate SIEM findings in parallel with your team. Security Incident Response Engineering helps identify correlations across hybrid and multi-cloud environments and assists with scoping threat actor activity across providers. @@ -98 +98 @@ AWS Security Incident Response doesn't directly ingest findings from your SIEM. -AWS SIRT also collaborates directly with your MDR providers and third-party investigation teams to help establish effective coordination processes before an incident occurs. +Security Incident Response Engineering also collaborates directly with your MDR providers and third-party investigation teams to help establish effective coordination processes before an incident occurs.