chore: unify bold syntax to single asterisk in .org files and update legacy memex-amero references
This commit is contained in:
@@ -4,7 +4,7 @@
|
||||
#+FILETAGS: :infrastructure:security:hardening:psf:
|
||||
|
||||
* Overview
|
||||
The **Infrastructure** project governs the physical and virtual foundations of the Memex. It ensures high availability, security hardening, and operational transparency across cloud and local resources.
|
||||
The *Infrastructure* project governs the physical and virtual foundations of the Memex. It ensures high availability, security hardening, and operational transparency across cloud and local resources.
|
||||
|
||||
* Phase A: Demand (PRD)
|
||||
:PROPERTIES:
|
||||
@@ -15,10 +15,10 @@ The **Infrastructure** project governs the physical and virtual foundations of t
|
||||
Define the requirements for a secure, resilient, and documented infrastructure posture.
|
||||
|
||||
** 2. User Needs
|
||||
- **Security Hardening:** Implementation of the OpenClaw security audit findings.
|
||||
- **Vulnerability Management:** Regular risk assessments and reporting.
|
||||
- **Inventory Control:** Complete mapping of cloud and local assets.
|
||||
- **Roadmap Planning:** 30/60/90 day infrastructure evolution.
|
||||
- *Security Hardening:* Implementation of the OpenClaw security audit findings.
|
||||
- *Vulnerability Management:* Regular risk assessments and reporting.
|
||||
- *Inventory Control:* Complete mapping of cloud and local assets.
|
||||
- *Roadmap Planning:* 30/60/90 day infrastructure evolution.
|
||||
|
||||
** 3. Success Criteria
|
||||
*** TODO Harden Docker port bindings (bind to 127.0.0.1)
|
||||
|
||||
Reference in New Issue
Block a user