diff --git a/develop/_sources/security.rst.txt b/develop/_sources/security.rst.txt
index b225c5228..0bf9a1d1f 100644
--- a/develop/_sources/security.rst.txt
+++ b/develop/_sources/security.rst.txt
@@ -8,7 +8,7 @@ Introduction
This document details the security framework for Open OnDemand, providing essential information that administrators need to know for secure deployment and operation.
.. note::
- If you're here to report a vulerability, you may refer to :ref:`vulnerability-management`.
+ If you're here to report a vulnerability, you may refer to :ref:`vulnerability-management`.
Considerations
--------------
@@ -38,19 +38,58 @@ that some centers may want to change or disable altogether.
Additionally, you may want to disable or limit access to the application. You can do this
through :ref:`disabling_applications`.
-Conclusion
-----------
-Maintaining a secure and robust operational environment is critical for the success of Open OnDemand. Administrators are encouraged to implement the security practices recommended in this guide and to regularly review security settings and updates.
+.. _vulnerability-management:
+
+Vulnerability Management
+------------------------
+
+Vulnerability management is a critical component of the security strategy for Open OnDemand.
+This document outlines the procedures for reporting and managing vulnerabilities.
+
+Reporting a Vulnerability
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+If you have security concerns or think you have found a vulnerability, please submit a
+private report by visiting the 'Security' section of our GitHub located at
+`GitHub Open OnDemand Security `_ and
+clicking 'Report a vulnerability'.
+
+For direct inquiries or issues in submitting a report, contact the core project team
+via email at security@openondemand.org.
+
+Disclosure Policy
+^^^^^^^^^^^^^^^^^
+
+- Upon reporting, you will receive a response within hours, acknowledging the receipt of the report.
+- A primary handler from the team will be assigned to coordinate the fix and release process:
+- Confirm the problem and determine the affected versions (1-2 days).
+- Audit code to find any potential similar problems.
+- Prepare fixes for all releases still under maintenance and release as soon as possible.
+
+Comments on Policy
+^^^^^^^^^^^^^^^^^^
+
+Suggestions to improve this process can be made via submitting a ticket, opening a
+Discourse topic, or a pull request.
+
+Security Audits
+^^^^^^^^^^^^^^^
+
+Open OnDemand has been audited several times by Trusted CI, the NSF Cybersecurity
+Center of Excellence. The latest engagement report is available
+`here `__.
+These audits have helped shape the security landscape of the platform and contribute
+to its ongoing security enhancements.
+
+
+Maintaining a secure and robust operational environment is critical for the success of
+Open OnDemand. Administrators are encouraged to implement the security practices
+recommended in this guide and to regularly review security settings and updates.
Relevant References
-------------------
-.. toctree::
- :maxdepth: 2
- :caption: Security Topics
-
- security/vulnerability-management
- authentication/overview
- how-tos/monitoring/logging
- customizations
+- :ref:`Authentication Overview `
+- :ref:`Logging `
+- :ref:`Customizations `
diff --git a/develop/_sources/security/vulnerability-management.rst.txt b/develop/_sources/security/vulnerability-management.rst.txt
deleted file mode 100644
index b23168dea..000000000
--- a/develop/_sources/security/vulnerability-management.rst.txt
+++ /dev/null
@@ -1,42 +0,0 @@
-.. _vulnerability-management:
-
-Vulnerability Management
-========================
-
-Introduction
-------------
-
-Vulnerability management is a critical component of the security strategy for Open OnDemand. This document outlines the procedures for reporting and managing vulnerabilities.
-
-Reporting a Vulnerability
--------------------------
-
-If you have security concerns or think you have found a vulnerability, please submit a private report by visiting the 'Security' section of our GitHub located at `GitHub Open OnDemand Security `_ and clicking 'Report a vulnerability'.
-
-For direct inquiries or issues in submitting a report, contact the core project team via email at security@openondemand.org.
-
-Disclosure Policy
------------------
-
-- Upon reporting, you will receive a response within hours, acknowledging the receipt of the report.
-- A primary handler from the team will be assigned to coordinate the fix and release process:
-- Confirm the problem and determine the affected versions (1-2 days).
-- Audit code to find any potential similar problems.
-- Prepare fixes for all releases still under maintenance and release as soon as possible.
-
-Comments on Policy
-------------------
-
-Suggestions to improve this process can be made via submitting a ticket, opening a Discourse topic, or a pull request.
-
-Security Audits
----------------
-
-Open OnDemand has been audited several times by Trusted CI, the NSF Cybersecurity Center of Excellence. The latest engagement report is available `here `__. These audits have helped shape the security landscape of the platform and contribute to its ongoing security enhancements.
-
-Conclusion
-----------
-
-Effective vulnerability management is crucial for maintaining the security and integrity of Open OnDemand. Users and contributors play a vital role in this process by reporting potential security vulnerabilities through GitHub, ensuring the platform's continued safety.
-
-.. note:: For details on the specific vulnerability management steps, please see the GitHub repository guidelines or the security policies linked above.
diff --git a/develop/authentication/overview.html b/develop/authentication/overview.html
index ea96296ed..dbc1bdd84 100644
--- a/develop/authentication/overview.html
+++ b/develop/authentication/overview.html
@@ -102,9 +102,33 @@
Maintaining a secure and robust operational environment is critical for the success of Open OnDemand. Administrators are encouraged to implement the security practices recommended in this guide and to regularly review security settings and updates.
Vulnerability management is a critical component of the security strategy for Open OnDemand.
+This document outlines the procedures for reporting and managing vulnerabilities.
If you have security concerns or think you have found a vulnerability, please submit a
+private report by visiting the ‘Security’ section of our GitHub located at
+GitHub Open OnDemand Security and
+clicking ‘Report a vulnerability’.
+
For direct inquiries or issues in submitting a report, contact the core project team
+via email at security@openondemand.org.
Open OnDemand has been audited several times by Trusted CI, the NSF Cybersecurity
+Center of Excellence. The latest engagement report is available
+here.
+These audits have helped shape the security landscape of the platform and contribute
+to its ongoing security enhancements.
+
Maintaining a secure and robust operational environment is critical for the success of
+Open OnDemand. Administrators are encouraged to implement the security practices
+recommended in this guide and to regularly review security settings and updates.
Vulnerability management is a critical component of the security strategy for Open OnDemand. This document outlines the procedures for reporting and managing vulnerabilities.
If you have security concerns or think you have found a vulnerability, please submit a private report by visiting the ‘Security’ section of our GitHub located at GitHub Open OnDemand Security and clicking ‘Report a vulnerability’.
-
For direct inquiries or issues in submitting a report, contact the core project team via email at security@openondemand.org.
Open OnDemand has been audited several times by Trusted CI, the NSF Cybersecurity Center of Excellence. The latest engagement report is available here. These audits have helped shape the security landscape of the platform and contribute to its ongoing security enhancements.
Effective vulnerability management is crucial for maintaining the security and integrity of Open OnDemand. Users and contributors play a vital role in this process by reporting potential security vulnerabilities through GitHub, ensuring the platform’s continued safety.
-
-
Note
-
For details on the specific vulnerability management steps, please see the GitHub repository guidelines or the security policies linked above.