diff --git a/en_US.ISO8859-1/books/handbook/security/chapter.xml b/en_US.ISO8859-1/books/handbook/security/chapter.xml
index 631cbfd068..c49b18a7ca 100644
--- a/en_US.ISO8859-1/books/handbook/security/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/security/chapter.xml
@@ -3172,13 +3172,29 @@ You are advised to update or deinstall the affected package(s) immediately.&os; Security Advisories
- Like many production quality operating systems, &os;
- publishes Security Advisories. These
- advisories are usually mailed to the security lists and noted
- in the Errata only after the appropriate releases have been
- patched. This section explains what an advisory is, how to
- understand it, and what measures to take in order to patch a
- system.
+ Like many producers of quality operating systems, the &os;
+ Project has a security team which is responsible for
+ determining the End-of-Life (EoL) date for each
+ &os; release and to provide security updates for supported
+ releases which have not yet reached their
+ EoL. More information about the &os;
+ security team and the supported releases is available on the
+ &os; security
+ page.
+
+ One task of the security team is to respond to reported
+ security vulnerabilities in the &os; operating system. Once a
+ vulnerability is confirmed, the security team verifies the steps
+ necessary to fix the vulnerability and updates the source code
+ with the fix. It then publishes the details as a
+ Security Advisory. Security
+ advisories are published on the &os; website
+ and mailed to the &a.security-notifications.name;,
+ &a.security.name;, and &a.announce.name; mailing lists.
+
+ This section describes the format of a &os;
+ security advisory.What Does an Advisory Look Like?