Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Report
Data sources: ZENODO
addClaim

ASD Category Lock Packet v1.0: Field Definition, Technical Standard v1.1, and Architecture

Authors: sparks, kurt;

ASD Category Lock Packet v1.0: Field Definition, Technical Standard v1.1, and Architecture

Abstract

Active‑Session Defense (ASD) is introduced in this publication as a new field of privacy‑first, non‑surveillance mobile safety architecture. The ASD Category Lock Packet v1.0 formally defines the field, establishes the Technical Standard v1.1 terminology, specifies the 10‑module ASD architecture, and documents the federal framework alignment that governs ASD’s design. ASD operates at the active‑session layer of mobile devices to provide real‑time possession assurance, coercion and duress detection, grooming‑risk detection without accessing message content, and session‑level Zero Trust enforcement. All ASD safety functions rely exclusively on behavioral, contextual, and device‑native signals. No communications content, message metadata, or stored personal data is collected, analyzed, or retained. This packet freezes the canonical definitions, module boundaries, and architectural constraints for ASD v1.0 through a formal Category Lock. It supersedes all prior governance‑platform or compliance‑framework characterizations and establishes ASD as a distinct technical discipline aligned with NIST SP 800‑207 (Zero Trust Architecture), the NIST Privacy Framework, Safety by Design, Responsible AI (NIST AI RMF), COPPA, and federal mobile security guidance. This Zenodo record provides a permanent, citable reference for the foundational ASD architecture and serves as the authoritative source for all future ASD research, documentation, and implementation work

Powered by OpenAIRE graph
Found an issue? Give us feedback