AWS Security ChangesHomeSearch

AWS security-ir documentation change

Service: security-ir · 2025-12-16 · Documentation low

File: security-ir/latest/userguide/eradicate.md

Summary

Replaced 'AWS CIRT' with 'AWS Security Incident Response engineers' in eradication phase guidance.

Security assessment

Terminology standardization without indication of resolving a security flaw. Part of routine documentation maintenance.

Diff

diff --git a/security-ir/latest/userguide/eradicate.md b/security-ir/latest/userguide/eradicate.md
index 38b22864d..38f9c903b 100644
--- a//security-ir/latest/userguide/eradicate.md
+++ b//security-ir/latest/userguide/eradicate.md
@@ -9 +9 @@ During the eradication phase, it is important to identify and address all affect
-It is a best practice to use a phased approach to eradication and recovery, and to prioritize remediation steps. The purpose of the early phases is to increase the overall security quickly (days to weeks) with high-value changes to prevent future events. The later phases can focus on longer-term changes (for example, infrastructure changes), and ongoing work to keep the enterprise as secure as possible. Each case is unique and AWS CIRT will work with you to assess necessary actions. 
+It is a best practice to use a phased approach to eradication and recovery, and to prioritize remediation steps. The purpose of the early phases is to increase the overall security quickly (days to weeks) with high-value changes to prevent future events. The later phases can focus on longer-term changes (for example, infrastructure changes), and ongoing work to keep the enterprise as secure as possible. Each case is unique and AWS Security Incident Response engineers will work with you to assess necessary actions.