Homepage Discordian Blog ISMS Reference Verification and Correction

[pethers]

Objective: Verify and correct all discordian*.html blog page references to ensure they point to the correct ISMS policies in Hack23/ISMS repository.

Background: Analysis of Hack23/ISMS shows that Acceptable_Use_Policy.md and Physical_Security_Policy.md already exist. All major topic areas referenced by homepage blog pages have coverage in ISMS, though some are distributed across multiple policies.

Tasks:

1. Verify Current References:

   • Review all discordian-*.html files for ISMS policy links
   • Document current references vs. actual ISMS structure
   • Identify broken or incorrect links

2. Create Reference Mapping Table:

   Blog Page	Current Reference	Correct ISMS Reference	Status	Notes
   discordian-email-security.html	Email_Security_Policy.md (?)	Network_Security_Policy.md (§ Email Security Architecture)	⚠️ Verify	Email security covered in Network policy
   discordian-cloud-security.html	Cloud_Security_Policy.md (?)	Network_Security_Policy.md + Access_Control_Policy.md + SUPPLIER.md (AWS)	⚠️ Verify	Distributed coverage
   discordian-physical-security.html	Physical_Security_Policy.md	Physical_Security_Policy.md	✅ Correct	Policy exists
   discordian-acceptable-use.html	Acceptable_Use_Policy.md	Acceptable_Use_Policy.md	✅ Correct	Policy exists
   discordian-monitoring-logging.html	Monitoring_Logging_Policy.md (?)	Secure_Development_Policy.md + Network_Security_Policy.md + Security_Metrics.md	⚠️ Verify	Distributed coverage
   discordian-remote-access.html	Remote_Access_Policy.md (?)	Mobile_Device_Management_Policy.md + Access_Control_Policy.md	⚠️ Verify	Remote access covered in MDM policy
   discordian-security-training.html	Security_Awareness_Training_Policy.md (?)	Information_Security_Policy.md (training section)	⚠️ Verify	Training requirements in main policy
   discordian-data-protection.html	Data_Protection_Policy.md (?)	Privacy_Policy.md + Data_Classification_Policy.md	⚠️ Verify	Data protection split across two policies

3. Update Blog Pages:

   • Correct all ISMS policy links to point to actual existing policies
   • Add section anchors where coverage is within larger policies (e.g., Network_Security_Policy.md#email-security)
   • For distributed coverage, link to primary policy with annotation

4. Documentation:

   • Update homepage README with correct ISMS reference structure
   • Create ISMS_REFERENCE_GUIDE.md mapping blog topics to ISMS policies
   • Ensure all links use correct GitHub URLs (Hack23/ISMS, not ISMS-PUBLIC if applicable)

Acceptance Criteria:

• ✅ All discordian-*.html pages link to existing ISMS policies
• ✅ No broken links to non-existent policies
• ✅ Reference guide created documenting ISMS coverage structure
• ✅ Links tested and verified working

Priority: High - Public-facing blog should accurately reflect ISMS structure
Effort: Medium - Verification and link updates across ~30-40 blog pages