This page collects the documents for the three QASO (Quantum Agentic Security Operations) products: Secure, Assure, and security orchestration, automation, and response (SOAR). Start with a one-page overview, read the four-page manager guide, plan an evaluation, or open the full product book.
SECURE · ASSURE · SOAR
Open the documents you need.
Short material for managers, with full references for detailed review.
Secure
Secure
Exposure management: reachable systems, known weaknesses, and attack paths on the networks you authorize. Not proof the network is complete.
Full product book. Opens Google sign-in, which a network without internet access cannot use. The one-page overview and four-page manager guide are public portable document format (PDF) files.
Assure
Assure
Code security: each code finding checked against the exact line. Engineering candidate; not yet approved for your source code, for installation at your site, or for production use.
Detection and response: flags failed-login bursts in the logs you send it and unusual connections in packet metadata (source, destination, destination port, and size) and NetFlow (records of which systems talked to which), then drafts a response; approval follows its risk class (the lowest risk class is logged by policy, with no approval record). Not a security information and event management (SIEM) system.
Full product book. Opens Google sign-in, which a network without internet access cannot use. The one-page overview and four-page manager guide are public portable document format (PDF) files.
What each product can show about post-quantum cryptography (PQC).
Post-quantum cryptography is new encryption and signature algorithms designed to resist attacks by quantum computers. See what each product contributes: Secure records the key exchange each service selects in a test connection (not certificates) and compares post-quantum timing numbers you enter, Assure lists the cryptography the code calls, and SOAR drafts responses for approval by risk class. QASO does not perform or prove a migration, and nothing re-checks automatically after a change; a new scan or import shows the new state.