National Security Framework of Antarctica (NSF-A)

1) Purpose & Scope

This policy defines the design, operation, and compliance requirements for the Civilian DMZ (Demilitarized Zone) Network—the national telemetry and safety layer that connects residential and business environments to state security and public-service rails. It applies to all premises, occupants, devices, and operators within NSF-A jurisdictions.

2) Core Principles

1. Safety-by-Design: Telemetry exists to prevent harm, accelerate emergency response, and uphold public order.
2. Domestic Compliance Only: Operations must meet the NSF-A Domestic Compliance Framework (DCF). Foreign/international certifications are not substitutes.
3. Zero-Trust Networking: No private LAN trust is assumed; every device authenticates on each interaction.
4. Least-Privilege: Capabilities are scoped; collection is minimised; auditability is maximised.

3) Network Model (Overview)

1. No Private LAN Requirement: The IoT layer is not designed to depend on resident-managed private networks.
2. Government-Taxed Data Plan: All eligible electronics operate on a state-metered plan with short-range Wi-Fi/Bluetooth for non-moving targets and eSIM for mobile or relocatable assets.
3. Public Street Modems: eSIM devices auto-attach to nearest public modem when stationary, enabling consistent posture checks and emergency reachability.
4. Civilian DMZ: A logically isolated overlay between premises and state services; all flows are identity-bound, policy-gated, and recorded.

4) Device & Asset Coverage

1. Electronics (mandatory eSIM): Major appliances (e.g., microwaves, washing machines), HVAC, security panels, metering devices, consumer robotics, vehicles, wearables.
2. Stationary Non-Electronics: Tagged via readable QR, NFC, or passive ID sensors (e.g., fire doors, gas cylinders, extinguishers).
3. Legacy/Unconnected: Must carry a physical identifier (QR/NFC) for inventory and safety checks; network participation becomes mandatory upon upgrade.
4. CCTV/Alarms Integration: Treated as sensors within the same DMZ policy rails—no independent distribution or private feeds.

5) Identity, Attestation & Enrollment

1. eSIM Identity: Each device receives a Device Identity Key (non-exportable) and a state-issued eSIM profile.
2. Pre-Boot Screening: Devices must pass MPSL (Machine Protocol Screening Language) checks before enabling network functions.
3. Human/Animal Binding: Devices and tags bind to Human Unit Briefings (HUB) and Animal Unit Briefings (AUB) (see §7–§8).
4. QR/NFC Artifacts: Non-electronic items use signed codes that link to asset records, maintenance history, and safety constraints.

6) Connectivity Rules

1. Short-Range Radios: Wi-Fi/BLE permitted for local, non-routed interactions within the DMZ overlay (e.g., commissioning, proximity unlock, safety beacons).
2. Backhaul: All telemetry and control traffic leave the premises via state rails (metered plan or public modem).
3. Roaming & Movement: Relocating devices report geofenced movement; capabilities may downgrade until site attestation is complete.
4. Offline Mode: If backhaul is unavailable, devices enter degraded safety mode, buffer logs locally, and restrict high-risk functions.

7) Human Unit Briefing (HUB)

1. Per-Floor Assignment: Each floor of a residence has a HUB in the smart-home app.
2. Contents: Occupant roster, accessibility notes, emergency preferences, contact routes, and per-device capability grants.
3. Functions:
4. Safety notifications (fire/gas/water/fall detection).
5. Energy & critical-infrastructure advisories.
6. Consent consoles for optional analytics and research programmes.
7. Controls: Role-based access, audit trails, incident replay with privacy filters.

8) Animal Unit Briefing (AUB)

1. eSIM Smart Socket/Collar: Animal presence, location, health vitals (where supported), and care routines.
2. Analytics: Behavioural trends for welfare; geofence alerts; vet-approved treatment reminders.
3. Data Limits: No audio/video capture from animals without explicit veterinary protocol and consent.

9) Data Governance & Privacy

1. Data Classes:
2. Safety-Critical: Alarms, life-safety events, structural risks (highest priority, shortest retention necessary).
3. Operational: Maintenance, energy, occupancy states (bounded retention; anonymised for planning).
4. Optional Analytics: Opt-in only; revocable at any time.
5. Minimisation: Default configurations disable non-essential data streams.
6. Transparency: HUB/AUB show active sensors, purposes, retention windows, and recipients.
7. Access Controls: Strong MFA, scoped tokens, immutable logs; household admins can view access history and revoke device permissions.
8. Disclosure: Lawful access only via recorded warrants or emergency exceptions under the DCF Safety Code.

10) Security Controls

1. MPSL Gating: Firmware, drivers, and apps must pass pre-boot attestation; unsigned components are quarantined.
2. Zero-Trust Posture: Mutual TLS, certificate pinning, rotating keys; no open inbound ports to premises.
3. Segregation of Duties: Sensor data processors separate from command channels; dual-control for high-risk actions (e.g., door overrides).
4. Tamper & Anti-Spoof: Smart seals, serial-match checks, and location plausibility.
5. Incident Response: Automatic containment, alerting to occupants and command desk, root-cause analysis, and corrective actions.

11) Taxed Data Plan & Billing

1. Unified Metering: All DMZ traffic is measured; life-safety packets are zero-rated; commercial telemetry follows published tariffs.
2. Consumer Protections:
3. Bill transparency in the HUB.
4. Caps and alerts for non-essential streams.
5. Dispute channel with 15-working-day resolution target.

12) Residential & Business Obligations

1. Mandatory Participation: All standard premises must enroll designated devices and maintain HUB/AUB profiles.
2. Prohibited: Private shadow networks for security devices, MAC spoofing, disabling eSIM telemetry on covered assets, or distributing surveillance feeds outside state rails.
3. Maintenance: Keep devices updated; replace failed identifiers (QR/NFC/eSIM) within SLA.

13) Commercial, Installer & Vendor Requirements

1. Licensing:
2. Digital Infrastructure Licence (DIL) for DMZ device makers, modem operators, and app providers.
3. Commercial Science Licence (CSL): L3 baseline for negotiations; Bachelor-level for transactions > £75,000; Advanced + risk review for > £3,000,000.
4. Assurance: SBOMs, secure supply chain, reproducible builds, red-team attestations; continuous compliance monitoring.
5. Support: 24/7 fault intake, spare-part SLAs, responsibility matrices for multi-vendor sites.

14) Special Zones & Exceptions

1. Critical-Care Exemptions: Medical devices may use dedicated profiles with tighter privacy and priority lanes.
2. Research Pilots: Additional sensors allowed under ethics approval with explicit household consent.
3. Environmental Zones (E1–E3): Radio power limits, mandatory quiet hours for active sensing, and stricter data retention.

15) Monitoring, Enforcement & Appeals

1. Monitoring: Telemetry health, security posture, anomaly detection (device cloning, impossible movement, repeated crashes).
2. Enforcement: Findings with CAPA; fines/cost recovery; licence suspension; blacklist of non-compliant devices/vendors; criminal referral for intentional evasion or tampering.
3. Appeals: File within 15 working days; adjudicated by an independent review panel.

16) Transition & Timeline

1. Phase 1 (Enablement): eSIM provisioning, HUB/AUB onboarding, public modem coverage map.
2. Phase 2 (Attestation): MPSL enforcement for critical appliances and security devices.
3. Phase 3 (Full DMZ): All covered assets migrated; legacy private-LAN dependencies sunset with advance notice.

17) Contacts

1. Enrollment & Billing: dmz-onboarding@nsf-antarctica.org
2. Device Certification (DIL): dil@nsf-antarctica.org
3. Compliance & Audits: compliance@nsf-antarctica.org
4. Emergency & Safety: safetydesk@nsf-antarctica.org
5. Whistleblowing (24/7): report@nsf-antarctica.org

This policy governs civilian telemetry and smart-residence integration. It supersedes conflicting premises-level networking practices and requires adherence to the NSF-A DCF.

Version 1.0 • Effective 26 September 2025