--- marp: true --- # nKode --- # Defining the Problem - Historical Context - Passwords as cornerstone of "something you know" authentication since 1961 (MIT's Compatible Time-Sharing System) - No major reinvention in over 60 years, despite evolving threats - Key Problems in Authentication - High cognitive load: 12-16 character passwords rotated every 60-90 days; prone to reuse and errors under stress - Vulnerabilities: Hacked at 95 per second globally; susceptible to phishing, keyloggers, and credential harvesting - Tactical Edge Challenges: Difficult with tactical gear (e.g., gloves); bypassed in high-risk, low-bandwidth environments; limits multi-factor authentication (MFA) --- # Current State of the Art - Relies on static inputs: Keyboards, text-based passwords, and mental models outdated for modern threats - Alternatives like biometrics (facial/iris/fingerprint/voice): Effective in ideal conditions but constrained in low-light, noisy, or gloved scenarios - Emerging Tech: Zero Trust, edge computing, AI-driven security in systems like Tactical Assault Kits—but compromised by AI attacks, signals intelligence, and nation-state exploits --- # How nKode Aligns with DARPA ERIS - Topic area fit: Advances resilience, efficiency, and effectiveness for strategic systems across critical infrastructure and military C2 at strategic, command, operational, and tactical edges. - Mission tie: Supports DARPA’s aim to create technological surprise for U.S. national security. - nKode’s role: Reinvents “something you know” with keyboard-less, AI-generated icons to keep auth working in contested or low-bandwidth networks. - Surprise element: Resilient to credential reuse and keyloggers; can operate over unencrypted or bandwidth-constrained links without exposing secrets. - Operational benefits: Faster, low-cognitive-load access under stress; reduces bypasses and maintains mission continuity for edge tools like TAK. - Architectural alignment: Complements Zero Trust, edge computing, and secure operations in dynamic, degraded conditions. - Impact: Hardens C2 and critical infrastructure against AI-driven credential harvesting and disruption in contested environments. --- # Current Approaches vs. nKode - How the Problem Is Addressed Today - Long, complex passwords (12–16 chars), rotated every 60–90 days - Prone to reuse, keyloggers, shoulder surfing; high cognitive load under stress - Requires keyboards (impractical with tactical gear); MFA often needs secure channels - High global breach cadence; controls get bypassed in high-risk environments - Biometrics (face/iris/fingerprint): fragile under duress, dirt, gloves, or low light - What’s New in nKode’s Approach - Patented virtual keypad with shuffling icons; AI-generated, user-unique icon sets - Vs. Passwords: No text entry; strong guessing resistance with compact inputs - Vs. Biometrics: No special hardware; reliable under pressure and harsh conditions - Backend uses a CSPRNG (e.g., ChaCha20) to drive shuffling over low-trust links - Resilient to keyloggers and replay; auto-rotation without user action; shoulder-surf resistant - Field-ready path with TRL 5 progression - Why It Matters at the Edge - Works in low-bandwidth or contested environments - Cuts cognitive load and speeds access, reducing bypass behavior - Preserves mission continuity for edge tools and C2 workflows --- # Foreseen Barriers - Adoption Risk: Authentication changes are high-risk; companies hesitant to be first adopters - Pitch History: Positive feedback from dozens (e.g., FIS, banks) over 10 years, but no implementations - Technical: Integration with legacy DoD systems; user training; device compatibility (rugged tablets) - Evolving Threats: Advanced AI shoulder-surfing; scaling to millions/billions of unique, psychologically neutral icons to prevent AI prediction of user selections - Mitigation: Leverage ERIS for rapid pathways; partner with McCrary Institute for validation --- # Why nKode Will Succeed - Market Validation: Independent survey by User Insight – 52% prefer nKode (vs. 28% passwords) - High Acceptance: 17% above "very high" benchmark (35%) - Team Strength: Veterans with cyber ops experience; TRL 5 proven - Dual-Use Potential: Defense (tactical edge) + Commercial - Evidence: Exceeds benchmarks; low friction deployment --- # Proposed Plan/Strategy if Funded - Phase 1: Adapt commercial app for tactical edge; integrate with ATACs/Tactical Assault Kits - Phase 2: Field validation/testing in simulated environments; address barriers (training/integration) - Phase 3: Advance to TRL 6-7; deploy OpenID Connect for DoD systems - Timeline: 12-18 months; focus on low-bandwidth resilience - Outcomes: Prototype for warfighters; pathway to commercialization --- # Arcanum and McCrary Technical Team pictures --- # Defense and Commercial Market Use Case/Impact - Defense Use Cases - Tactical edge authentication: Secure access to Tactical Assault Kits/comms platforms in DDIL environments - Warfighter resilience: Keyboard-less icons reduce errors under stress; resists keyloggers, phishing, AI attacks - Zero Trust enablement: Auth over unencrypted/low-bandwidth channels; integrates with C2 systems/edge compute - Commercial Use Cases - Banking/Healthcare/Infrastructure: Replaces passwords for online accounts; phishing-resistant, no credential reuse - Dual-Use Potential: Scales to consumer apps; reduces MFA friction in high-volume sectors - Market Impact ("So What") - Enhances mission success/safety: Faster logins, fewer vulnerabilities in contested ops - Broad Adoption: Safeguards critical ops across sectors