SHIELD / ATLAS
Software-Defined Dual-Use National Emergency Management & C2 Platform
ISS LLC / SecureAssure · Service-Disabled Veteran-Owned Small Business (SDVOSB pending)
Dr. Terry Flood, PMP · US Army (Retired) · terry@issdefense.com · shield-atlas-production.up.railway.app
Brand voice — locked 2026-04-23
“Train as we fight. Fight tonight.” · “Work smarter, not harder.” · “We enhance, we don’t compete.” · “Every user is a sensor.” · “Integrate. Analyze. Interpret. Disseminate. In real time.”
Company Identity
Legal NameISS LLC (DBA SecureAssure)
CAGE Code9VKK3
UEIC7YDV3P8EHL7
SAM.govActive
Set-AsideSDVOSB (pending VA verification)
NAICS (primary)541512 / 541330 / 541715 / 541611
PSCD316 / R425 / DA01 / R408
Place of PerformanceCONUS · OCONUS · Coalition
Point of Contact
PrincipalDr. Terry Flood, PMP
ServiceUS Army (Retired)
Emailterry@issdefense.com
Live Platformshield-atlas-production.up.railway.app
Evaluator URL (no login)/evaluate
Guided Demo/?demo=guided — <8 min, all 5 wedges
The Five Wedges — how we show
01 · Counter-UAS (C-UAS)
Software-defined detect / classify / decide against Group 1 & Group 2 UAS, fiber-optic FPV, and Geran/Shahed-class decoy storms. We compress the kill chain — we don’t replace the shooter.
/airspace · /swarm-c2 · /cram-dashboard · /kill-chain-simulation
02 · Maritime & Critical Infrastructure
Global AIS, 785 NOAA buoys, 56 ports, 21 risk zones — in-browser, no SeaVision-class subscription, no second login. USCG, NORTHCOM, MARAD, port authorities, state EM.
/maritime · /dod-cop
03 · Planning & Wargaming
Train-as-we-fight sandbox — the same code path as LIVE. Kill-chain, kill-web, joint-ops, DIME-PMESII, all instrumented and replayable.
/sandbox · /kill-chain-simulation · /kill-web · /joint-ops · /dime-pmesii
04 · U2U Comms (Every User Is A Sensor)
Browser-only mobile hub. No MDM, no app store, seconds to onboard. Camera, voice tactical, NL command, photo+GPS, lowlight, ambassador community report, live video from the field.
/mobile-hub · /unit-demo · /phone · /ambassador · /live
05 · Open Architecture + Audit + Dual-Use
MOSA-aligned (10 USC 4401). PNT including timing. STANAG-4586 / 5516 / 4676, MIL-STD-2525D, CoT/TAK. Tamper-evident hash-chain audit + dual-key Engagement Safety Gate — defensible to JAG, IG, OGC, and Congress. The same platform serves civil EOCs and warfighters — one training pipeline, one procurement.
/governance · /security · /gps-denied · /joint-ops · /dod-cop · /cop
The Twelve DoD / FEMA Needs Solved — why it matters
| # | Need (in their words) | Stakeholder pain owner | Wedge | Live route |
|---|---|---|---|---|
| 01 | Stop trading $1M interceptors for $300 drones | NORTHCOM, USAF AFGSC, SOCOM, FEMA mass-event lead | C-UAS | /airspace |
| 02 | One picture: air, sea, land, cyber, space | JADC2 PMO, COCOM J3/J6, MARFORPAC, USCG sector | All five | /dod-cop |
| 03 | Sensor-to-shooter inside the adversary’s loop | Service component G3/J3, Joint Fires, FSCOORD | C-UAS + Plan | /kill-chain-simulation |
| 04 | Escape vendor lock-in (MOSA is statutory, 10 USC 4401) | DoD CIO, SAEs, JADC2 architect office, prime PMs | Open Arch | /governance |
| 05 | Operate when GPS / comms are degraded (DDIL) | INDOPACOM, EUCOM, USTRANSCOM, USCG remote ops | Open Arch | /gps-denied |
| 06 | Coalition + ally interop without bilateral integration projects | AUKUS Pillar II, NATO ACT, FVEY, allied liaison | Open Arch | /joint-ops |
| 07 | Train on the same system you’ll fight on tonight | TRADOC, MCCDC, Joint Staff J7, FEMA training branch | Plan + War | /sandbox |
| 08 | Every soldier (and every responder) actually IS a sensor | Service G2/G6, ATAK PO, FEMA region IMTs | U2U | /mobile-hub |
| 09 | Unit-to-unit voice & text that won’t cost six figures per node | Bn S6, USCG sector ops, FEMA ESF-2 (comms) | U2U | /mobile-hub |
| 10 | Maritime + port + critical-infrastructure awareness without SeaVision-class subscription | USCG, NORTHCOM, MARAD, ports, state EM | Maritime | /maritime |
| 11 | Mass-event + all-hazards EOC that’s the same platform as the warfighter’s | FEMA Regions, state EM, city OEM, World Cup ‘26 / Olympics | Dual-Use | /cop |
| 12 | AI you can defend in front of a JAG, an IG, and Congress | DoD GC, OSD Policy, JAG, OIG, Congressional staff | Open Arch | /governance |
Differentiators
ArchitectureOpen / MOSA / data-centric
DeploymentBrowser-first, zero-install, no MDM
OnboardingSeconds, not weeks
AI postureHuman-judgment-centric · multi-vendor · auditable
Audit postureTamper-evident hash-chain · dual-key Engagement Safety Gate
Dual-useSame platform: civil EOC + warfighter
Train modeSame code path as LIVE
Coalition8 STANAGs · CoT/TAK live today
Cost-Asymmetry, By the Numbers
vs C-UAS RF appliance (per-node)~100× lower
vs stovepiped C2 console suite$250K–$2M / yr replaced
vs SeaVision-class maritime sub$200K–$800K / yr replaced
vs separate JCATS/AFSIM sim$300K–$1M / yr replaced
vs per-bilateral integration project$200K–$1M each avoided
vs hardware radio at lower echelon$50K–$200K / yr replaced
Marginal device cost$0 (browser, BYOD)
Standards & Compliance Anchors
MOSA (10 USC 4401)
CoT / TAK / ATAK / WinTAK / iTAK
STANAG-4586
STANAG-5516
STANAG-4676
MIL-STD-2525D
CMMC 2.0 Level 2 (target)
FedRAMP-aligned
PNT incl. Timing (T)
DDIL-tolerant
JADC2 / DBE-aligned
UK MOD AI Strategy — AI Now / AI Next
DIME-PMESII
F2T2EA
Live Today on Railway
Active modules66
Routed dashboards39 (with global nav, 6-echelon switcher, cost chip)
Federal data sources28+ (live: NOAA, FIRMS, OpenSky, NWS, USGS, AIS, SAM.gov)
Evaluator path/evaluate — no login
Guided demo/?demo=guided — 7 steps, <8 min
HostingRailway (auto-deploy from GitHub main)
What Live Looks Like (honest disclosure)
Where a capability is intentionally stubbed today (e.g., multi-AI audit lanes 2–4, certain cached intel surfaces), the dashboard reads as a labeled virtual guide: operator does X → sees Y → action Z. We do not claim live unless live. The five canonical wedge briefs at
/docs/canonical/0X_*_wedge.md walk through both the live demo and the “what live looks like” future-state, in the same brand voice.
Roadmap — Next 12 Months (29 pathways beyond the 66 shipping today)
The headline number on this statement — 66 modules — counts only what is wired into
MODULE_MANIFEST and live on the running server today. Earlier marketing surfaces quoted 95 by bundling the 66 shipping modules with 29 planned / in-flight / pilot pathways. Those 29 are real engineering work the team is building toward over the next 12 months and are listed here so evaluators can see the trajectory without us inflating the headline number. Status legend: planned = scoped, not yet in active build · in-flight = active code under development against the spec · pilot = limited deployment with one or more design partners. See /docs/MODULE_COUNT_RECONCILIATION.md for full audit history.
| # | Roadmap module | Bucket | Status | Target |
|---|---|---|---|---|
| R-01 | PQC Tactical Messenger — CNSA 2.0 (ML-KEM + ML-DSA) hybrid suite | PQC / Comms | in-flight | Q3 2026 |
| R-02 | Hybrid TLS 1.3 with PQC key exchange across all platform endpoints | PQC / Comms | in-flight | Q3 2026 |
| R-03 | ML-DSA code-signing pipeline for tactical bundle distribution | PQC / Comms | planned | Q4 2026 |
| R-04 | Cryptographic inventory + legacy RSA/ECC deprecation playbook | PQC / Comms | planned | Q4 2026 |
| R-05 | Coalition selective-release messaging gateway (FVEY / NATO release flags) | PQC / Comms | planned | Q1 2027 |
| R-06 | Mobile FIRES screen — 9-line CFF + AFATDS/VMF/CoT export from phone | Mobile parity | in-flight | Q3 2026 |
| R-07 | Mobile POSEIDON screen — AEGIS / TRIDENT / NEPTUNE on tablet | Mobile parity | planned | Q4 2026 |
| R-08 | Mobile SPECTRUM screen — emitter tracking, EMCON, jamming-ops | Mobile parity | planned | Q4 2026 |
| R-09 | Mobile ODIN MDMP wizard — mission analysis / COA / IPB on-device | Mobile parity | planned | Q1 2027 |
| R-10 | Mobile CBRN / plume modeling screen with on-device MOPP guidance | Mobile parity | planned | Q1 2027 |
| R-11 | Mobile evidentiary-capture screen — geo-tagged, hash-chained on capture | Mobile parity | pilot | Q3 2026 |
| R-12 | Tamper-evident hash-chain investigative export bundle generator | Evidentiary | in-flight | Q3 2026 |
| R-13 | Classification-aware after-action reconstruction packager | Evidentiary | planned | Q4 2026 |
| R-14 | Court-admissible chain-of-custody manifest generator (FRE-aligned) | Evidentiary | planned | Q4 2026 |
| R-15 | JAG / IG / OGC selective-release redaction packager (per-recipient policy) | Evidentiary | planned | Q1 2027 |
| R-16 | ESMS swarm-track fusion sub-module — many-on-many decoy-storm classification | Dual-use sub | in-flight | Q3 2026 |
| R-17 | ESMS counter-FOC (fiber-optic-controlled FPV) detection sub-module | Dual-use sub | pilot | Q3 2026 |
| R-18 | POSEIDON ASW convergence-zone fusion sub-module | Dual-use sub | planned | Q4 2026 |
| R-19 | C-RAM auto-routed counter-battery fire-mission sub-module | Dual-use sub | pilot | Q3 2026 |
| R-20 | GUARDIAN APT threat-actor enrichment sub-module (MITRE ATT&CK auto-correlation) | Dual-use sub | planned | Q4 2026 |
| R-21 | METRO city/county multi-tenant isolation sub-module (per-jurisdiction data fences) | Dual-use sub | planned | Q4 2026 |
| R-22 | DIME-PMESII automated 1st/2nd/3rd-order effects modeler | Dual-use sub | in-flight | Q3 2026 |
| R-23 | Maritime port-authority adapter (port-side AIS + SeaVision-class ingest) | Dual-use sub | planned | Q1 2027 |
| R-24 | Cost-aware effector allocation with burn-rate alerting (Bundle B-05) | Sensor / Effector | in-flight | Q3 2026 |
| R-25 | Weapon-target pairing sub-module (Pk + cost + magazine + role) | Sensor / Effector | in-flight | Q3 2026 |
| R-26 | Eight parallel-equal feed fallbacks for DDIL transport (Bundle B-06) | Sensor / Effector | planned | Q4 2026 |
| R-27 | GPS-denied PNT including Timing (T) backup over the 7 PNT methods | Sensor / Effector | planned | Q4 2026 |
| R-28 | SIPRNet ingest adapter (sponsor- and ATO-gated) | Sensor / Effector | planned | Q1 2027 |
| R-29 | IL-5 GovCloud deployment path with CAC/PIV + FIPS 140-3 modules | Sensor / Effector | planned | Q2 2027 |
66 + 29 = 95. The 29 above are roadmap pathways, not capabilities currently in
MODULE_MANIFEST. They will only be promoted into the headline 66 figure (and that figure incremented) once each item is wired into the runtime registry, exposed by the live server, and verifiable at /api/modules/registry.