Update index.html
Browse files- index.html +451 -19
index.html
CHANGED
|
@@ -1,19 +1,451 @@
|
|
| 1 |
-
<!
|
| 2 |
-
<html>
|
| 3 |
-
|
| 4 |
-
|
| 5 |
-
|
| 6 |
-
|
| 7 |
-
|
| 8 |
-
|
| 9 |
-
|
| 10 |
-
|
| 11 |
-
|
| 12 |
-
|
| 13 |
-
|
| 14 |
-
|
| 15 |
-
|
| 16 |
-
|
| 17 |
-
|
| 18 |
-
|
| 19 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
<!DOCTYPE html>
|
| 2 |
+
<html lang="en">
|
| 3 |
+
<head>
|
| 4 |
+
<meta charset="UTF-8">
|
| 5 |
+
<meta name="viewport" content="width=device-width, initial-scale=1.0">
|
| 6 |
+
<title>Baltimore Secure Backbone System (BSBS) – Portfolio</title>
|
| 7 |
+
<style>
|
| 8 |
+
:root {
|
| 9 |
+
--outer-harbor: #2E86AB;
|
| 10 |
+
--inner-harbor: #3B5998;
|
| 11 |
+
--fort-mchenry: #1B2A4A;
|
| 12 |
+
--accent: #f4a261;
|
| 13 |
+
--bg: #f8f9fa;
|
| 14 |
+
--text: #212529;
|
| 15 |
+
--table-stripe: #e9ecef;
|
| 16 |
+
--box-bg: #ffffff;
|
| 17 |
+
}
|
| 18 |
+
body {
|
| 19 |
+
font-family: 'Segoe UI', Tahoma, Geneva, Verdana, sans-serif;
|
| 20 |
+
background: var(--bg);
|
| 21 |
+
color: var(--text);
|
| 22 |
+
line-height: 1.6;
|
| 23 |
+
margin: 0;
|
| 24 |
+
padding: 20px;
|
| 25 |
+
}
|
| 26 |
+
.container {
|
| 27 |
+
max-width: 1000px;
|
| 28 |
+
margin: 0 auto;
|
| 29 |
+
background: var(--box-bg);
|
| 30 |
+
padding: 2rem 3rem;
|
| 31 |
+
box-shadow: 0 2px 10px rgba(0,0,0,0.05);
|
| 32 |
+
border-radius: 8px;
|
| 33 |
+
}
|
| 34 |
+
h1, h2, h3 {
|
| 35 |
+
font-weight: 600;
|
| 36 |
+
}
|
| 37 |
+
h1 {
|
| 38 |
+
color: var(--fort-mchenry);
|
| 39 |
+
border-bottom: 2px solid var(--outer-harbor);
|
| 40 |
+
padding-bottom: 0.3em;
|
| 41 |
+
}
|
| 42 |
+
h2 {
|
| 43 |
+
color: var(--inner-harbor);
|
| 44 |
+
border-left: 5px solid var(--outer-harbor);
|
| 45 |
+
padding-left: 10px;
|
| 46 |
+
margin-top: 2em;
|
| 47 |
+
}
|
| 48 |
+
h3 {
|
| 49 |
+
color: var(--fort-mchenry);
|
| 50 |
+
}
|
| 51 |
+
.section-title {
|
| 52 |
+
color: var(--outer-harbor);
|
| 53 |
+
font-size: 1.8rem;
|
| 54 |
+
margin-top: 1.5em;
|
| 55 |
+
}
|
| 56 |
+
table {
|
| 57 |
+
border-collapse: collapse;
|
| 58 |
+
width: 100%;
|
| 59 |
+
margin: 1em 0;
|
| 60 |
+
font-size: 0.9rem;
|
| 61 |
+
}
|
| 62 |
+
th {
|
| 63 |
+
background-color: var(--outer-harbor);
|
| 64 |
+
color: white;
|
| 65 |
+
padding: 10px;
|
| 66 |
+
text-align: left;
|
| 67 |
+
}
|
| 68 |
+
td {
|
| 69 |
+
padding: 8px 10px;
|
| 70 |
+
border-bottom: 1px solid #ddd;
|
| 71 |
+
}
|
| 72 |
+
tr:nth-child(even) td {
|
| 73 |
+
background-color: var(--table-stripe);
|
| 74 |
+
}
|
| 75 |
+
.code-box, pre {
|
| 76 |
+
background: #1e1e1e;
|
| 77 |
+
color: #d4d4d4;
|
| 78 |
+
padding: 15px;
|
| 79 |
+
border-radius: 5px;
|
| 80 |
+
overflow-x: auto;
|
| 81 |
+
font-family: 'Courier New', monospace;
|
| 82 |
+
font-size: 0.85rem;
|
| 83 |
+
line-height: 1.4;
|
| 84 |
+
border: 1px solid #333;
|
| 85 |
+
}
|
| 86 |
+
.ascii-diagram {
|
| 87 |
+
font-family: 'Courier New', monospace;
|
| 88 |
+
white-space: pre;
|
| 89 |
+
background: #0d1b2a; /* dark navy background for diagrams */
|
| 90 |
+
color: #e0e0e0;
|
| 91 |
+
padding: 15px;
|
| 92 |
+
border-radius: 6px;
|
| 93 |
+
margin: 1em 0;
|
| 94 |
+
font-size: 0.8rem;
|
| 95 |
+
border-left: 4px solid var(--outer-harbor);
|
| 96 |
+
}
|
| 97 |
+
.outer { color: #2E86AB; font-weight: bold; }
|
| 98 |
+
.inner { color: #3B5998; font-weight: bold; }
|
| 99 |
+
.fort { color: #a2c4da; font-weight: bold; } /* lighter blue for navy bg */
|
| 100 |
+
.terminal { color: #f4a261; font-weight: bold; }
|
| 101 |
+
.hsm { color: #e76f51; font-weight: bold; }
|
| 102 |
+
|
| 103 |
+
.badge {
|
| 104 |
+
display: inline-block;
|
| 105 |
+
padding: 2px 8px;
|
| 106 |
+
border-radius: 12px;
|
| 107 |
+
font-size: 0.75rem;
|
| 108 |
+
background: var(--outer-harbor);
|
| 109 |
+
color: white;
|
| 110 |
+
margin-right: 5px;
|
| 111 |
+
}
|
| 112 |
+
.acronym-list dd {
|
| 113 |
+
margin-bottom: 0.5em;
|
| 114 |
+
}
|
| 115 |
+
.footer {
|
| 116 |
+
margin-top: 3em;
|
| 117 |
+
font-size: 0.85rem;
|
| 118 |
+
color: #6c757d;
|
| 119 |
+
border-top: 1px solid #ccc;
|
| 120 |
+
padding-top: 1em;
|
| 121 |
+
text-align: center;
|
| 122 |
+
}
|
| 123 |
+
a {
|
| 124 |
+
color: var(--outer-harbor);
|
| 125 |
+
text-decoration: none;
|
| 126 |
+
}
|
| 127 |
+
a:hover {
|
| 128 |
+
text-decoration: underline;
|
| 129 |
+
}
|
| 130 |
+
</style>
|
| 131 |
+
</head>
|
| 132 |
+
<body>
|
| 133 |
+
<div class="container">
|
| 134 |
+
|
| 135 |
+
<h1>Baltimore Secure Backbone System (BSBS)</h1>
|
| 136 |
+
<p><strong>Comprehensive Portfolio Submission</strong><br>
|
| 137 |
+
<em>Municipal Cybersecurity Governance, Post‑Quantum Architecture, and Constitutional Compliance</em></p>
|
| 138 |
+
<p><strong>Author:</strong> [Your Name] | <strong>Course:</strong> [Capstone / Cybersecurity Governance & Technical Architecture] | <strong>Date:</strong> June 2, 2026 | <strong>Version:</strong> 2.1 (Final Portfolio)</p>
|
| 139 |
+
|
| 140 |
+
<h2>Table of Contents</h2>
|
| 141 |
+
<ol>
|
| 142 |
+
<li>Abstract & Portfolio Overview</li>
|
| 143 |
+
<li>BSBS Policy Addendum v1.0</li>
|
| 144 |
+
<li>Artifact A – NIST SP 800‑53 Rev. 5 Control Mapping</li>
|
| 145 |
+
<li>Artifact B – Fourth Amendment Minimization Protocol (Legal Memorandum)</li>
|
| 146 |
+
<li>Artifact C – Technical Architecture Diagrams (Vivid ASCII)</li>
|
| 147 |
+
<li>Reflective Analysis & Feasibility Assessment</li>
|
| 148 |
+
<li>Lessons Learned & Professional Growth</li>
|
| 149 |
+
<li>References</li>
|
| 150 |
+
<li>Appendix A – Acronym Glossary</li>
|
| 151 |
+
<li>Appendix B – Diagram Rendering Notes</li>
|
| 152 |
+
</ol>
|
| 153 |
+
|
| 154 |
+
<!-- ================= 1. Abstract ================= -->
|
| 155 |
+
<h2>1. Abstract & Portfolio Overview</h2>
|
| 156 |
+
<p>The Baltimore Secure Backbone System (BSBS) is a multidisciplinary cybersecurity framework that demonstrates upper‑division competency in governance, legal analysis, post‑quantum cryptography, memory‑safe systems programming, and machine‑learning‑driven threat detection. This portfolio artifact positions BSBS not as a theoretical exercise, but as a realistic, jurisprudentially‑informed technical architecture for a mid‑sized American city.</p>
|
| 157 |
+
<p><strong>Learning Outcomes Demonstrated:</strong></p>
|
| 158 |
+
<ul>
|
| 159 |
+
<li>Design and justification of a zero‑trust municipal network segmentation model (Concentric Harbor)</li>
|
| 160 |
+
<li>Application of NIST Risk Management Framework (RMF) and control mapping to a moderate‑impact system</li>
|
| 161 |
+
<li>Integration of transitional post‑quantum cryptography (Kyber, Dilithium, SPHINCS+) into existing infrastructure</li>
|
| 162 |
+
<li>Constitutional compliance engineering: Fourth Amendment minimization protocols and oversight mechanics</li>
|
| 163 |
+
<li>Memory‑safe protocol hardening using Rust and formal verification (Kani)</li>
|
| 164 |
+
<li>Incident response planning aligned with CJIS, HIPAA, and state breach notification laws</li>
|
| 165 |
+
</ul>
|
| 166 |
+
|
| 167 |
+
<!-- ================= 2. Policy Addendum ================= -->
|
| 168 |
+
<h2>2. BSBS Policy Addendum v1.0 – Municipal Cybersecurity Framework</h2>
|
| 169 |
+
|
| 170 |
+
<h3>2.1 Executive Summary</h3>
|
| 171 |
+
<p>The Baltimore Secure Backbone System (BSBS) is a comprehensive cybersecurity governance and technical architecture framework designed to protect the City of Baltimore’s municipal data infrastructure against current cryptographic threats and future post‑quantum adversarial capabilities. BSBS operates as a zero‑trust municipal backbone integrating constitutional privacy safeguards, NIST‑aligned risk management, and transitional post‑quantum cryptographic protocols.</p>
|
| 172 |
+
<p><strong>Scope:</strong> All 47 municipal departments, Baltimore City Public Schools data interfaces, Baltimore Police Department (BPD) CJIS‑compliant systems, Baltimore City Health Department genomic/bioinformatics pipelines, and critical infrastructure OT/ICS networks (water, waste, transit).</p>
|
| 173 |
+
<p><strong>Authority:</strong> Derived from Baltimore City Code Article 1, Subtitle 40 (Information Technology); Maryland Criminal Procedure Code §10‑301 (CJIS compliance); and Fourth Amendment constraints on municipal data collection and retention.</p>
|
| 174 |
+
|
| 175 |
+
<h3>2.2 Governance & Legal Architecture</h3>
|
| 176 |
+
<table>
|
| 177 |
+
<tr><th>Layer</th><th>Entity</th><th>Function</th></tr>
|
| 178 |
+
<tr><td>Strategic</td><td>Mayor’s Office of Cybersecurity (MOC)</td><td>Policy authorization, budgetary control, intergovernmental liaison</td></tr>
|
| 179 |
+
<tr><td>Tactical</td><td>BSBS Security Operations Center (BSOC)</td><td>24/7 monitoring, incident response, threat intelligence</td></tr>
|
| 180 |
+
<tr><td>Operational</td><td>Departmental Information Security Officers (DISOs)</td><td>Department‑level control implementation, user access governance</td></tr>
|
| 181 |
+
<tr><td>Audit</td><td>Baltimore City Inspector General (IG) + External NIST 800‑53A assessors</td><td>Annual control assessment, constitutional compliance review</td></tr>
|
| 182 |
+
</table>
|
| 183 |
+
<p><strong>Constitutional & Statutory Compliance Matrix:</strong></p>
|
| 184 |
+
<ul>
|
| 185 |
+
<li><strong>Fourth Amendment:</strong> Network monitoring uses metadata‑only analysis with differential privacy; content inspection requires DISO authorization + IG notification.</li>
|
| 186 |
+
<li><strong>Maryland Public Information Act (MPIA):</strong> Encryption does not obstruct lawful records requests; retention schedules published.</li>
|
| 187 |
+
<li><strong>CJIS Security Policy v5.9:</strong> FIPS 140‑3 Level 2 validated modules for biometric and criminal history data.</li>
|
| 188 |
+
<li><strong>HIPAA / 42 CFR Part 2:</strong> Segregated encryption domains for SUD records.</li>
|
| 189 |
+
</ul>
|
| 190 |
+
|
| 191 |
+
<h3>2.3 Threat Model & Risk Framework</h3>
|
| 192 |
+
<table>
|
| 193 |
+
<tr><th>Threat Vector</th><th>Actor</th><th>Impact</th><th>BSBS Control</th></tr>
|
| 194 |
+
<tr><td>Ransomware (OT/ICS)</td><td>Criminal syndicates / RaaS</td><td>Water treatment disruption, transit halt</td><td>Air‑gapped OT enclaves, immutable backup architecture</td></tr>
|
| 195 |
+
<tr><td>Store‑Now‑Decrypt‑Later (SNDL)</td><td>Nation‑state adversaries</td><td>Decryption of municipal archives</td><td>Post‑quantum hybrid key encapsulation (Kyber768+X25519)</td></tr>
|
| 196 |
+
<tr><td>Supply Chain (Bioinformatics)</td><td>APT targeting genomic pipelines</td><td>Tampering of genomic data</td><td>Rust‑based memory‑safe emulation, reproducible build verification</td></tr>
|
| 197 |
+
<tr><td>Insider Threat (Law Enforcement)</td><td>Authorized user exfiltration</td><td>CJIS data breach, 4th Amendment litigation</td><td>Attribute‑Based Encryption (ABE) with judicial logging</td></tr>
|
| 198 |
+
<tr><td>Municipal IoT Botnet</td><td>Distributed attackers</td><td>Smart city sensor compromise, DDoS</td><td>Micro‑segmentation, device attestation via Dilithium signatures</td></tr>
|
| 199 |
+
</table>
|
| 200 |
+
<p><strong>Risk Score</strong> = (Threat Likelihood × PSI × CLR × FI) / Normalization Factor, where PSI = Public Safety Impact, CLR = Constitutional Litigation Risk, FI = Fiscal Impact.</p>
|
| 201 |
+
|
| 202 |
+
<h3>2.4 Technical Architecture</h3>
|
| 203 |
+
<p><strong>Network Segmentation: The “Concentric Harbor” Model</strong></p>
|
| 204 |
+
<div class="ascii-diagram">
|
| 205 |
+
<span class="outer">┌─────────────────────────────────────────────────────────────┐</span>
|
| 206 |
+
<span class="outer">│ OUTER HARBOR (Untrusted Internet / Public WiFi / IoT) │</span>
|
| 207 |
+
<span class="outer">│ Post-Quantum TLS 1.3 (Hybrid X25519Kyber768) │</span>
|
| 208 |
+
<span class="outer">├─────────────────────────────────────────────────────────────┤</span>
|
| 209 |
+
<span class="inner">│ INNER HARBOR (Municipal Enterprise / Dept VLANs) │</span>
|
| 210 |
+
<span class="inner">│ mTLS with Dilithium-3 signatures; SDP │</span>
|
| 211 |
+
<span class="inner">├─────────────────────────────────────────────────────────────┤</span>
|
| 212 |
+
<span class="fort">│ FORT McHENRY (CJIS / Critical Infrastructure / OT) │</span>
|
| 213 |
+
<span class="fort">│ Air-gapped or unidirectional data diodes; FIPS 140-3 HSMs │</span>
|
| 214 |
+
<span class="fort">│ Classical + PQC hybrid; manual key ceremony for root CAs │</span>
|
| 215 |
+
<span class="fort">└─────────────────────────────────────────────────────────────┘</span>
|
| 216 |
+
</div>
|
| 217 |
+
|
| 218 |
+
<p><strong>Post‑Quantum Cryptographic Implementation:</strong></p>
|
| 219 |
+
<table>
|
| 220 |
+
<tr><th>Layer</th><th>Primitive</th><th>Implementation</th><th>Purpose</th></tr>
|
| 221 |
+
<tr><td>Key Encapsulation</td><td>ML‑KEM‑768 (Kyber)</td><td>liboqs + custom Rust wrapper</td><td>Hybrid KEM with X25519</td></tr>
|
| 222 |
+
<tr><td>Digital Signatures</td><td>ML‑DSA‑65 (Dilithium)</td><td>Pure Rust implementation</td><td>Device attestation, code signing, document integrity</td></tr>
|
| 223 |
+
<tr><td>Hashing / Backup</td><td>SHA‑3‑256 + SPHINCS+</td><td>Thales Luna 7 HSM</td><td>Long‑term archive integrity</td></tr>
|
| 224 |
+
<tr><td>OT/ICS</td><td>Lightweight PQC (future on‑ramp candidates)</td><td>Gateway translation layer</td><td>SCADA device protection</td></tr>
|
| 225 |
+
</table>
|
| 226 |
+
<p><strong>Transitional Strategy (2024‑2035):</strong> Phase 1 – Hybrid X25519Kyber768; Phase 2 – Dilithium‑3 for software updates; Phase 3 – Full PQC migration, classical deprecation.</p>
|
| 227 |
+
<p>The <em>Anomalous Pattern Inference Engine (APIE)</em> uses transformer‑based self‑attention to process encrypted traffic metadata (packet timing, entropy) without decryption, preserving Fourth Amendment minimization.</p>
|
| 228 |
+
|
| 229 |
+
<h3>2.5 Pure Rust HSPA Emulator: Legacy Protocol Hardening</h3>
|
| 230 |
+
<table>
|
| 231 |
+
<tr><th>Component</th><th>Specification</th></tr>
|
| 232 |
+
<tr><td>Language</td><td>Rust (edition 2021), <code>#![forbid(unsafe_code)]</code> in cryptographic path</td></tr>
|
| 233 |
+
<tr><td>Target</td><td>3GPP TS 25.214 (HSPA physical layer), TS 25.322 (RLC/MAC)</td></tr>
|
| 234 |
+
<tr><td>Security Features</td><td>Constant‑time operations; formal verification via Kani model checker</td></tr>
|
| 235 |
+
<tr><td>Integration</td><td>Legacy HSPA device → Rust emulator → TLS 1.3 + Kyber768 backbone</td></tr>
|
| 236 |
+
<tr><td>Constitutional Safeguard</td><td>Warrant buffer with IG notification; audit trail via Merkle tree (Dilithium‑signed)</td></tr>
|
| 237 |
+
</table>
|
| 238 |
+
|
| 239 |
+
<h3>2.6 Incident Response & Resilience (BMIRP aligned with NIST SP 800‑61 Rev. 2)</h3>
|
| 240 |
+
<table>
|
| 241 |
+
<tr><th>Phase</th><th>BSBS Action</th><th>Constitutional/Legal Check</th></tr>
|
| 242 |
+
<tr><td>Detection</td><td>APIE anomaly scoring + BSOC SIEM</td><td>Metadata vs. content review</td></tr>
|
| 243 |
+
<tr><td>Analysis</td><td>Forensic imaging to immutable S3 Glacier (Dilithium‑signed)</td><td>IG notification if BPD data involved</td></tr>
|
| 244 |
+
<tr><td>Containment</td><td>SDP segmentation; OT air‑gap activation</td><td>Mayor’s Office authorization for citywide actions</td></tr>
|
| 245 |
+
<tr><td>Eradication</td><td>Re‑image from SPHINCS+ verified gold‑masters</td><td>Evidence preservation</td></tr>
|
| 246 |
+
<tr><td>Recovery</td><td>Phased restoration with enhanced monitoring</td><td>Public notification per Maryland PIPA if PII impacted</td></tr>
|
| 247 |
+
<tr><td>Post‑Incident</td><td>After‑action report; APIE retraining</td><td>IG review of any surveillance expansion</td></tr>
|
| 248 |
+
</table>
|
| 249 |
+
|
| 250 |
+
<h3>2.7 Implementation Roadmap</h3>
|
| 251 |
+
<table>
|
| 252 |
+
<tr><th>Phase</th><th>Timeline</th><th>Deliverable</th><th>Budget Estimate</th></tr>
|
| 253 |
+
<tr><td>I. Governance</td><td>Months 1‑3</td><td>MOC charter; DISO appointments; IG audit protocol</td><td>$150K</td></tr>
|
| 254 |
+
<tr><td>II. Backbone Hardening</td><td>Months 4‑9</td><td>Concentric Harbor deployment; hybrid PQC TLS</td><td>$2.1M</td></tr>
|
| 255 |
+
<tr><td>III. Legacy Emulation</td><td>Months 6‑12</td><td>Rust HSPA emulator; water/SCADA integration</td><td>$890K</td></tr>
|
| 256 |
+
<tr><td>IV. AI/ML Security</td><td>Months 10‑15</td><td>APIE deployment; federated learning infrastructure</td><td>$1.2M</td></tr>
|
| 257 |
+
<tr><td>V. Full PQC Transition</td><td>2028‑2033</td><td>Classical deprecation; full Dilithium/Kyber authority</td><td>$500K/year</td></tr>
|
| 258 |
+
</table>
|
| 259 |
+
|
| 260 |
+
<h3>2.8 Metrics & Continuous Monitoring</h3>
|
| 261 |
+
<ul>
|
| 262 |
+
<li><strong>MTTD</strong> <15 minutes for critical infrastructure</li>
|
| 263 |
+
<li><strong>MTTR</strong> <2 hours for containment</li>
|
| 264 |
+
<li><strong>Post‑Quantum Readiness Score:</strong> 100% hybrid KEM TLS by Q2 2026</li>
|
| 265 |
+
<li><strong>Constitutional Compliance Score:</strong> 100% IG audits satisfactory</li>
|
| 266 |
+
<li><strong>Legacy System Security Coverage:</strong> 100% non‑replaceable OT devices protected</li>
|
| 267 |
+
</ul>
|
| 268 |
+
|
| 269 |
+
<h3>2.9 Conclusion</h3>
|
| 270 |
+
<p>BSBS treats constitutional constraints as design requirements, integrating post‑quantum cryptography, memory‑safe systems, and privacy‑preserving AI into a governance structure accountable to both technical standards and civil liberties.</p>
|
| 271 |
+
|
| 272 |
+
<!-- ================= 3. NIST Mapping ================= -->
|
| 273 |
+
<h2>3. Artifact A – NIST SP 800‑53 Rev. 5 Control Mapping <span class="badge">Moderate Baseline</span></h2>
|
| 274 |
+
<p><small>Hyperlinked control IDs open official NIST CSRC definitions in a new tab.</small></p>
|
| 275 |
+
<table>
|
| 276 |
+
<tr><th>Control ID</th><th>Control Name</th><th>BSBS Implementation</th><th>Evidence / Artifact</th></tr>
|
| 277 |
+
<tr><td><a href="https://csrc.nist.gov/projects/risk-management/sp800-53-controls/release-search#!/control?version=5.1&number=AC-3" target="_blank">AC‑3</a></td><td>Access Enforcement</td><td>Concentric Harbor & ABE</td><td>SDP logs, ABE policy files</td></tr>
|
| 278 |
+
<tr><td><a href="https://csrc.nist.gov/projects/risk-management/sp800-53-controls/release-search#!/control?version=5.1&number=AC-4" target="_blank">AC‑4</a></td><td>Information Flow Enforcement</td><td>Rust HSPA Emulator / Data Diodes</td><td>Kani formal verification</td></tr>
|
| 279 |
+
<tr><td><a href="https://csrc.nist.gov/projects/risk-management/sp800-53-controls/release-search#!/control?version=5.1&number=AU-10" target="_blank">AU‑10</a></td><td>Non‑Repudiation</td><td>Dilithium‑3 Signatures</td><td>Merkle‑tree logs with signed roots</td></tr>
|
| 280 |
+
<tr><td><a href="https://csrc.nist.gov/projects/risk-management/sp800-53-controls/release-search#!/control?version=5.1&number=CP-9" target="_blank">CP‑9</a></td><td>System Backup</td><td>SPHINCS+ signed backups</td><td>Hash‑validation logs</td></tr>
|
| 281 |
+
<tr><td><a href="https://csrc.nist.gov/projects/risk-management/sp800-53-controls/release-search#!/control?version=5.1&number=IA-2" target="_blank">IA‑2</a></td><td>Identification & Authentication</td><td>Hybrid PQC (Kyber768+X25519)</td><td>mTLS handshake logs</td></tr>
|
| 282 |
+
<tr><td><a href="https://csrc.nist.gov/projects/risk-management/sp800-53-controls/release-search#!/control?version=5.1&number=SC-8" target="_blank">SC‑8</a></td><td>Transmission Confidentiality</td><td>TLS 1.3 + ML‑KEM</td><td>PQC ciphersuite PCAPs</td></tr>
|
| 283 |
+
<tr><td><a href="https://csrc.nist.gov/projects/risk-management/sp800-53-controls/release-search#!/control?version=5.1&number=SC-38" target="_blank">SC‑38</a></td><td>Operations Security</td><td>APIE</td><td>Metadata‑only anomaly reports</td></tr>
|
| 284 |
+
<tr><td><a href="https://csrc.nist.gov/projects/risk-management/sp800-53-controls/release-search#!/control?version=5.1&number=SI-4" target="_blank">SI‑4</a></td><td>System Monitoring</td><td>Federated Learning / APIE</td><td>Minimization protocol audit logs</td></tr>
|
| 285 |
+
</table>
|
| 286 |
+
|
| 287 |
+
<!-- ================= 4. Fourth Amendment Memo ================= -->
|
| 288 |
+
<h2>4. Artifact B – Fourth Amendment Minimization Protocol (Legal Memorandum)</h2>
|
| 289 |
+
<p><strong>TO:</strong> Departmental Information Security Officers (DISOs), Baltimore City Public Schools, BPD<br>
|
| 290 |
+
<strong>FROM:</strong> Office of the General Counsel / Mayor’s Office of Cybersecurity (MOC)<br>
|
| 291 |
+
<strong>SUBJECT:</strong> Minimization Protocols for BSBS Network Monitoring and Data Retention<br>
|
| 292 |
+
<strong>DATE:</strong> May 23, 2024</p>
|
| 293 |
+
|
| 294 |
+
<h3>4.1 Purpose</h3>
|
| 295 |
+
<p>To ensure that BSBS provides robust cybersecurity while strictly adhering to the Fourth Amendment and the Baltimore City Charter regarding citizen privacy.</p>
|
| 296 |
+
|
| 297 |
+
<h3>4.2 Data Segregation and Minimization</h3>
|
| 298 |
+
<ul>
|
| 299 |
+
<li><strong>Metadata vs. Content:</strong> The APIE is prohibited from performing Deep Packet Inspection (DPI) on encrypted traffic content without a specific DISO‑issued warrant. Monitoring is restricted to network flow metadata.</li>
|
| 300 |
+
<li><strong>Differential Privacy:</strong> When aggregating threat intelligence, the APIE must apply a Laplacian noise mechanism to prevent reconstruction of any individual user’s behavior.</li>
|
| 301 |
+
</ul>
|
| 302 |
+
|
| 303 |
+
<h3>4.3 Warrant Requirements</h3>
|
| 304 |
+
<p>If decryption of traffic is required (using BSBS escrowed keys), the following must be documented:</p>
|
| 305 |
+
<ul>
|
| 306 |
+
<li>Probable cause of active malicious exfiltration or system compromise.</li>
|
| 307 |
+
<li>Narrow tailoring: specific enclave, IP range, and timeframe.</li>
|
| 308 |
+
<li>Automated notification to the City Inspector General within 4 hours.</li>
|
| 309 |
+
</ul>
|
| 310 |
+
|
| 311 |
+
<h3>4.4 Retention Limits</h3>
|
| 312 |
+
<p>Encryption‑related metadata purged every 90 days unless flagged in an active investigation. Long‑term SPHINCS+‑signed backups are strictly for disaster recovery and are not searchable for law enforcement without a judicial order.</p>
|
| 313 |
+
|
| 314 |
+
<!-- ================= 5. Diagrams (Vivid ASCII) ================= -->
|
| 315 |
+
<h2>5. Artifact C – Technical Architecture Diagrams <span class="badge">Vivid ASCII</span></h2>
|
| 316 |
+
<p>The following diagrams use terminal‑friendly color classes. When viewed in a terminal that supports ANSI, the colors will be vivid; here they are rendered with HTML span colors matching the harbor palette.</p>
|
| 317 |
+
|
| 318 |
+
<h3>Diagram A: Concentric Harbor Network Segmentation</h3>
|
| 319 |
+
<div class="ascii-diagram">
|
| 320 |
+
<span class="outer"> OUTER HARBOR (Untrusted) </span>
|
| 321 |
+
<span class="outer"> Public WiFi IoT Sensors </span>
|
| 322 |
+
<span class="outer"> | | </span>
|
| 323 |
+
<span class="outer"> +--------+---------+ </span>
|
| 324 |
+
<span class="outer"> | </span>
|
| 325 |
+
<span class="outer"> Hybrid TLS 1.3 Gateway </span>
|
| 326 |
+
<span class="outer"> | </span>
|
| 327 |
+
<span class="inner"> INNER HARBOR (Enterprise) </span>
|
| 328 |
+
<span class="inner"> | </span>
|
| 329 |
+
<span class="inner"> SDP Controller </span>
|
| 330 |
+
<span class="inner"> / \ </span>
|
| 331 |
+
<span class="inner"> Dept VLANs Health Dept / Genomic </span>
|
| 332 |
+
<span class="inner"> | | </span>
|
| 333 |
+
<span class="inner"> | | </span>
|
| 334 |
+
<span class="fort"> FORT McHENRY (Critical/OT) </span>
|
| 335 |
+
<span class="fort"> | | </span>
|
| 336 |
+
<span class="fort"> Data Diode Rust HSPA Emulator </span>
|
| 337 |
+
<span class="fort"> | | </span>
|
| 338 |
+
<span class="fort">SCADA/Water Legacy Bioinformatics </span>
|
| 339 |
+
<span class="fort"> | | </span>
|
| 340 |
+
<span class="fort"> +---- FIPS 140-3 HSM ----+ </span>
|
| 341 |
+
</div>
|
| 342 |
+
|
| 343 |
+
<h3>Diagram B: Post‑Quantum Hybrid Handshake Flow</h3>
|
| 344 |
+
<div class="ascii-diagram">
|
| 345 |
+
<span class="terminal"> Municipal Endpoint </span> <span class="outer"> BSBS Gateway (Rust) </span> <span class="hsm"> Thales Luna HSM </span>
|
| 346 |
+
| | |
|
| 347 |
+
| ClientHello | |
|
| 348 |
+
| (ECDHE_X25519 + | |
|
| 349 |
+
| ML-KEM-768) | |
|
| 350 |
+
|------------------------->| |
|
| 351 |
+
| | |
|
| 352 |
+
| | Request Private Key Op |
|
| 353 |
+
| |------------------------->|
|
| 354 |
+
| | |
|
| 355 |
+
| | Signed Response |
|
| 356 |
+
| | (ML-DSA-65) |
|
| 357 |
+
| |<-------------------------|
|
| 358 |
+
| | |
|
| 359 |
+
| ServerHello + | |
|
| 360 |
+
| ML-KEM Encapsulated Key| |
|
| 361 |
+
|<-------------------------| |
|
| 362 |
+
| | |
|
| 363 |
+
| Derive Shared Secret | |
|
| 364 |
+
| (Hybrid KEM) | |
|
| 365 |
+
| | |
|
| 366 |
+
| Finished (encrypted) | |
|
| 367 |
+
|------------------------->| |
|
| 368 |
+
| | |
|
| 369 |
+
| Finished | |
|
| 370 |
+
|<-------------------------| |
|
| 371 |
+
| | |
|
| 372 |
+
Secure Session Established | |
|
| 373 |
+
</div>
|
| 374 |
+
|
| 375 |
+
<!-- ================= 6. Reflective Analysis ================= -->
|
| 376 |
+
<h2>6. Reflective Analysis & Feasibility Assessment</h2>
|
| 377 |
+
<p><strong>Failure Mode Engineering:</strong> Fort McHenry (OT/CJIS) fails <em>closed</em> – data diodes sever if PQC latency exceeds threshold. Outer Harbor fails <em>open</em> – degrades to classical TLS 1.2 with heightened monitoring, ensuring public service continuity.</p>
|
| 378 |
+
<p><strong>Fiscal Sustainability:</strong> Open‑source PQC libraries and Rust avoid vendor lock‑in; HSPA emulator saves ~$4.2M over physical device replacement.</p>
|
| 379 |
+
<p><strong>Technical Validation:</strong> The Rust emulator is <code>#![forbid(unsafe_code)]</code> and formally verified with Kani, giving mathematical memory‑safety proof.</p>
|
| 380 |
+
<p><strong>Constitutional Robustness:</strong> Metadata‑only monitoring, warrant buffers, and IG notification align with <em>Carpenter v. United States</em> principles.</p>
|
| 381 |
+
|
| 382 |
+
<!-- ================= 7. Lessons Learned ================= -->
|
| 383 |
+
<h2>7. Lessons Learned & Professional Growth</h2>
|
| 384 |
+
<ul>
|
| 385 |
+
<li><strong>Governance is not an afterthought:</strong> Charter, audit, and budget are as critical as Kyber768.</li>
|
| 386 |
+
<li><strong>Legacy systems cannot be ignored:</strong> The emulator shows how to secure what cannot be replaced.</li>
|
| 387 |
+
<li><strong>Privacy is a design constraint:</strong> APIE proves threat detection can coexist with the Fourth Amendment.</li>
|
| 388 |
+
<li><strong>Integration matters:</strong> Combining policy, code, and law transforms assignments into professional artifacts.</li>
|
| 389 |
+
</ul>
|
| 390 |
+
|
| 391 |
+
<!-- ================= 8. References ================= -->
|
| 392 |
+
<h2>8. References</h2>
|
| 393 |
+
<ul>
|
| 394 |
+
<li>NIST. (2020). <em>NIST SP 800‑53 Rev. 5</em>. <a href="https://doi.org/10.6028/NIST.SP.800-53r5" target="_blank">https://doi.org/10.6028/NIST.SP.800-53r5</a></li>
|
| 395 |
+
<li>NIST. (2023). <em>FIPS 203, 204, 205</em>. <a href="https://csrc.nist.gov/projects/post-quantum-cryptography" target="_blank">PQC Project</a></li>
|
| 396 |
+
<li>Baltimore City Code, Article 1, Subtitle 40.</li>
|
| 397 |
+
<li>Maryland Criminal Procedure Code §10‑301.</li>
|
| 398 |
+
<li><em>Carpenter v. United States</em>, 585 U.S. ___ (2018).</li>
|
| 399 |
+
<li>Open Quantum Safe. <em>liboqs</em>. <a href="https://openquantumsafe.org/" target="_blank">openquantumsafe.org</a></li>
|
| 400 |
+
<li>Rust Foundation. <em>The Rust Programming Language</em>. <a href="https://doc.rust-lang.org/book/" target="_blank">doc.rust-lang.org</a></li>
|
| 401 |
+
<li>Kani Rust Verifier. <a href="https://model-checking.github.io/kani/" target="_blank">model-checking.github.io/kani</a></li>
|
| 402 |
+
</ul>
|
| 403 |
+
|
| 404 |
+
<!-- ================= 9. Acronym Glossary ================= -->
|
| 405 |
+
<h2>9. Appendix A – Acronym Glossary</h2>
|
| 406 |
+
<dl class="acronym-list">
|
| 407 |
+
<dt><strong>ABE</strong></dt><dd>Attribute‑Based Encryption</dd>
|
| 408 |
+
<dt><strong>APIE</strong></dt><dd>Anomalous Pattern Inference Engine</dd>
|
| 409 |
+
<dt><strong>BSBS</strong></dt><dd>Baltimore Secure Backbone System</dd>
|
| 410 |
+
<dt><strong>CJIS</strong></dt><dd>Criminal Justice Information Services</dd>
|
| 411 |
+
<dt><strong>DISO</strong></dt><dd>Departmental Information Security Officer</dd>
|
| 412 |
+
<dt><strong>FIPS</strong></dt><dd>Federal Information Processing Standards</dd>
|
| 413 |
+
<dt><strong>HSM</strong></dt><dd>Hardware Security Module</dd>
|
| 414 |
+
<dt><strong>IG</strong></dt><dd>Inspector General</dd>
|
| 415 |
+
<dt><strong>KEM</strong></dt><dd>Key Encapsulation Mechanism</dd>
|
| 416 |
+
<dt><strong>ML‑KEM</strong></dt><dd>Module‑Lattice‑based KEM (Kyber)</dd>
|
| 417 |
+
<dt><strong>ML‑DSA</strong></dt><dd>Module‑Lattice‑based Digital Signature Algorithm (Dilithium)</dd>
|
| 418 |
+
<dt><strong>MOC</strong></dt><dd>Mayor’s Office of Cybersecurity</dd>
|
| 419 |
+
<dt><strong>MPIA</strong></dt><dd>Maryland Public Information Act</dd>
|
| 420 |
+
<dt><strong>mTLS</strong></dt><dd>Mutual Transport Layer Security</dd>
|
| 421 |
+
<dt><strong>NIST</strong></dt><dd>National Institute of Standards and Technology</dd>
|
| 422 |
+
<dt><strong>OT/ICS</strong></dt><dd>Operational Technology / Industrial Control Systems</dd>
|
| 423 |
+
<dt><strong>PIPA</strong></dt><dd>Personal Information Protection Act (Maryland)</dd>
|
| 424 |
+
<dt><strong>PQC</strong></dt><dd>Post‑Quantum Cryptography</dd>
|
| 425 |
+
<dt><strong>PSI</strong></dt><dd>Public Safety Impact</dd>
|
| 426 |
+
<dt><strong>SDP</strong></dt><dd>Software‑Defined Perimeter</dd>
|
| 427 |
+
<dt><strong>SNDL</strong></dt><dd>Store‑Now‑Decrypt‑Later</dd>
|
| 428 |
+
<dt><strong>SPHINCS+</strong></dt><dd>Stateless hash‑based digital signature scheme</dd>
|
| 429 |
+
<dt><strong>SUD</strong></dt><dd>Substance Use Disorder</dd>
|
| 430 |
+
<dt><strong>TLS</strong></dt><dd>Transport Layer Security</dd>
|
| 431 |
+
</dl>
|
| 432 |
+
|
| 433 |
+
<!-- ================= 10. Diagram Rendering Notes ================= -->
|
| 434 |
+
<h2>10. Appendix B – Diagram Rendering Notes</h2>
|
| 435 |
+
<p>The ASCII diagrams above use the Baltimore “harbor” palette:</p>
|
| 436 |
+
<ul>
|
| 437 |
+
<li><span style="color:#2E86AB; font-weight:bold;">Outer Harbor (Teal #2E86AB)</span></li>
|
| 438 |
+
<li><span style="color:#3B5998; font-weight:bold;">Inner Harbor (Steel Blue #3B5998)</span></li>
|
| 439 |
+
<li><span style="color:#1B2A4A; font-weight:bold;">Fort McHenry (Navy #1B2A4A) – shown as lighter blue on dark background for readability</span></li>
|
| 440 |
+
<li><span style="color:#f4a261; font-weight:bold;">Municipal Endpoint (Orange #f4a261)</span></li>
|
| 441 |
+
<li><span style="color:#e76f51; font-weight:bold;">HSM (Dark Red #e76f51)</span></li>
|
| 442 |
+
</ul>
|
| 443 |
+
<p>These colors are applied via CSS classes in this HTML document. For terminal ANSI rendering, equivalent escape codes are used.</p>
|
| 444 |
+
|
| 445 |
+
<div class="footer">
|
| 446 |
+
<p>Baltimore Secure Backbone System (BSBS) – Portfolio v2.1 | [Your Name] | Capstone Submission June 2026</p>
|
| 447 |
+
</div>
|
| 448 |
+
|
| 449 |
+
</div>
|
| 450 |
+
</body>
|
| 451 |
+
</html>
|