Blog
Notes from the work.
Practical writing on post-quantum cryptography, legacy software modernization, and autonomous systems, including what the federal mandates and programs behind each one actually require.
Post-Quantum Cryptography
-
Post-Quantum IPsec VPN Migration: ML-KEM in IKEv2, Pre-Shared Keys, and What to Test Before Changing a Tunnel
How to move IPsec VPN tunnels to post-quantum key establishment: where the IKEv2 standards for ML-KEM stand in November 2026, how pre-shared key options compare, why message size matters, and how to catch silent fallback.
-
FIPS 140-3 Validation for Post-Quantum Cryptography: What Federal Buyers Should Check on a Module Certificate
A product that implements ML-KEM is different from a product that runs a FIPS 140-3 validated module with ML-KEM on its certificate. How to read a CMVP certificate for post-quantum algorithms, and what to ask suppliers.
-
Post-Quantum PKI Migration: Planning the Move to ML-DSA Certificates Before the 2031 Signature Deadline
How federal agencies and contractors can plan a public key infrastructure migration to ML-DSA certificates: what NIST IR 8547 says about PKI, parallel and composite hierarchies, certificate sizes, and the order in which to upgrade verifiers and issuers.
-
Post-Quantum Firmware Signing: Roots of Trust in Long-Lived Government and Defense Equipment
Signature verification that is fixed in hardware at manufacture cannot be migrated later. What NIST IR 8547, CNSA 2.0, and EO 14412 say about code signing, how ML-DSA, SLH-DSA, LMS, and XMSS compare, and what to ask suppliers.
-
Protecting Long-Lived Data From Harvest Now, Decrypt Later Collection
Harvest now, decrypt later risk depends on how long data must stay confidential. How to sort archives and traffic by retention, find exposed key wrapping, and sequence post-quantum fixes.
-
Federal PQC Mandates: EO 14412, OMB M-26-15, and CNSA 2.0
What EO 14412 and OMB M-26-15 require, how they fit with CNSA 2.0 and M-23-02, federal PQC migration deadlines, and what agencies and contractors should do now.
-
Post-Quantum Cryptography Migration Starts With an Inventory
Post-quantum cryptography migration fails without a cryptographic inventory. How to build a CBOM, prioritize by data lifetime, and test hybrid ML-KEM safely.
Legacy Modernization
-
COBOL to Java Migration: Rounding, Packed Decimal, and Sort Order Differences That Change Results
Translated code can be logically correct and still produce different payment amounts and differently ordered files. Where COBOL arithmetic and EBCDIC sorting differ from Java, C#, and Python defaults, and how a government program can test for it.
-
Legacy System Decommissioning: Writing the Disposition Plan for a Government System After Migration
Many modernization plans stop at go-live and leave the old system running. What GAO, NIST, and the National Archives expect when a legacy system is retired, and a shutdown sequence with exit conditions a program office can use.
-
Dependency Analysis Before a Legacy Migration: Unsupported Components and Undocumented Interfaces in Government Systems
How a government program can inventory what a legacy system depends on before migrating it: declared, vendored, platform, and interface dependencies, support status for each, and a migration order derived from the result.
-
Legacy System Data Migration: Cutover Plans, Go/No-Go Criteria, and Reconciliation for Government Programs
How government programs can reduce data migration risk when replacing a legacy system: mock conversions on current data, measurable go/no-go criteria, record-level reconciliation, and a funded post-installation phase.
-
Memory Safety Roadmaps for Legacy C and C++ Systems: Where Government Programs Should Start
How to build a memory safety roadmap for a legacy government system: inventory components and dependencies, pick harden, isolate, or replace per component, and verify behavior after each migration step.
-
AI Legacy Code Modernization Starts With Behavior, Not Syntax
AI legacy code modernization works when behavior is preserved: extract a behavior specification, gate every change with tests, and keep humans in approval.
-
Federal Legacy IT Modernization With AI: Evidence for the ATO
Federal legacy IT modernization with AI must produce evidence assessors can review, keep humans in approval, and run in disconnected, classified environments.
Robotics & Autonomy
-
AI Agent Identity and Delegation: How to Trace an Agent's Action Back to the Person Who Authorized It
Shared service accounts hide who authorized an AI agent's action. What NIST's 2026 agent identity work says about delegation, and how government programs can specify agent identities, on-behalf-of tokens, and audit records.
-
Securing AI Agent Tool Connections: What NSA's Model Context Protocol Guidance Means for Government Deployments
AI agents reach mission systems through tool connections, and NSA's May 2026 guidance on the Model Context Protocol treats that layer as its own security problem. How to register tool servers, separate trust zones, and enforce checks at a gateway.
-
Orchestrating Autonomous Systems in DDIL Environments: Pre-Authorized Envelopes, Lost-Link Behavior, and Reconciliation
How to design orchestration for autonomous platforms and AI agents when communications are denied, degraded, intermittent, or limited: bounded authority issued in advance, fallback rules per action class, and a reconnect protocol that puts deferred decisions back in front of a person.
-
AI Agent Orchestration in Mission Environments: Scoped Authority and Human Approval
How to orchestrate multiple AI agents in government and defense environments: scoped authority, approval tiers, and audit trails, aligned with 2026 joint agentic AI guidance.
-
Runtime Assurance for Autonomous Systems: Beyond Vehicle Health
Runtime assurance for autonomous systems means checking each course of action against mission contracts, with auditable evidence for DoD test and evaluation.
-
Tactile Sensing and Proprioception: What Robots Need to Feel
Why tactile sensing and robot proprioception matter more than vision for contact-rich manipulation, and how a shared somatosensory event schema could help.
Working on a hard technical problem?
We work with government organizations, research institutions, and technology teams across cybersecurity, software, and autonomous systems.