Last Updated: Aug 02, 2026
Claims and Independent Verification
Independently verified features were tested by third-party evaluators; some evaluations conducted under U.S. Government-sponsored contract activity including work involving the National Cyber Range Complex (NCRC). Reports and detailed findings are not always publicly releasable. U.S. Government-sponsored verifications may be discussed through authorized Government or customer channels.
The summary below identifies the capabilities that were independently reviewed or tested, what the evaluations confirmed, and why those findings matter to customers operating high-consequence industrial, infrastructure, defense, or mission environments.
| Capability Evaluated | What Independent Review Confirmed | Why It Matters |
|---|---|---|
| Real-time authentication | KST was evaluated for its ability to authenticate protected traffic before it is allowed to pass into the execution boundary using customer defined parameters for “real-time” operation. In tested scenarios KST exceeded those requirements. | Machines should not act on traffic just because it arrived. KST helps confirm that protected signals come from the expected source before they can affect operations – is it real, can it be trusted, should it exist now. |
| Per-message cryptographic protection, including encryption of payload | Independent review confirmed that KST uses a unique model and cryptographically sound protection methods at the message level rather than relying on session-level trust alone. | Compromise of one protected exchange cannot compromise the next. Each packet or signal must stand on its own. |
| Replay and spoofing resistance | Testing confirmed that captured or spoofed traffic could not be used to create valid protected exchanges in evaluated configurations. | Attackers often rely on replay, impersonation, or forged traffic. KST is designed to reject those attempts before they reach protected machines. |
| Boundary enforcement | Testing confirmed that unauthorized ingress and egress traffic could not cross protected boundaries in evaluated configurations. Testing further confirmed that authorized traffic within a cryptographic domain could not cross into adjacent domains unless authorized to do so. | KST helps create a hard trust boundary around systems that cannot afford to rely only on network reachability or monitoring. |
| Reconnaissance denial | Evaluators were unable to observe or infer protected endpoint behavior from outside the protected boundary in evaluated configurations. | If an attacker cannot see or map what is protected, they have less useful information to plan or execute an attack. |
| Configuration integrity | Testing confirmed that unauthorized or spoofed configuration attempts did not alter KST’s protected operating behavior. | Security controls are only valuable if attackers cannot remotely reconfigure them into a weaker state. |
| Resistance to traffic flooding | Testing confirmed that high-volume and overlay traffic did not force KST into unsafe fallback behavior in evaluated configurations. | Critical systems need controls that remain predictable under stress, not only under normal network conditions. |
| Hardware-rooted enforcement | Independent review confirmed that KST avoids conventional software and general-purpose operating-system attack surfaces. | Reducing software exposure lowers the number of ways an attacker can manipulate the protection layer itself. |
| Authentication-only operation | KST supports authentication without payload encryption, allowing protected traffic to remain visible where operations, maintenance, or monitoring require it. | Some customers need to trust traffic without hiding it from existing tools and personnel. KST can preserve visibility while still enforcing trust. |
| Selective encryption | KST can encrypt selected protected traffic when confidentiality is required, while allowing other protected traffic to remain visible. | Customers can protect sensitive payloads without forcing every system, workflow, or maintenance process into an encryption model. |
| No network-based key exchange | KST’s reviewed architecture does not depend on negotiating operational keys across the a network path, no key material is exchanged. | Attackers cannot compromise trust by attacking a conventional network key-exchange process that is not present in the protected path. |
| Low-latency operation | KST demonstrated sub-millisecond operation in evaluated performance testing with an average latency of ~0.11 ms for Authenticated and Encrypted M2M IP-based communications. NOTE: Serial and discrete-signal pathways were not included in the performance evaluation. Because those deployments remove portions of the IP/PHY processing stack and operate closer to the source signal, internal Blueskytec engineering measurements have observed substantially lower latency, including nanosecond-scale operation. | Industrial and machine-to-machine environments often cannot tolerate security controls that add meaningful delay. |
| Existing-system compatibility | KST was tested alongside existing controls, networks, and maintenance processes and verified to function without forcing changes to existing networks, data-flows or resource allocations. | Customers can add stronger trust enforcement through KST without starting over or replacing the systems they already depend on and have invested in. |
| Compromised-network operation | KST was tested against unauthorized, spoofed, and high-volume traffic in untrusted or adversarial network conditions and demonstrated the ability to function under such conditions with no performance or signal loss. | The surrounding network does not have to be clean before KST to enforce trust at the protected boundary. |
Government Affiliation and Non-Endorsement
Blueskytec America Inc., KST (Keyspace Technology), and all related products, services, materials, publications, demonstrations, presentations, and communications are provided by a private commercial entity. Blueskytec America Inc. is not an agency, instrumentality, representative, or official component of the United States Government, the U.S. Department of Defense, any Military Service, or any federal, state, or local government organization.
References to any government agency, military branch, command, program office, contract vehicle, operational environment, testing activity, facility, initiative, or public official are provided solely for factual, descriptive, historical, technical, interoperability, or informational purposes.
No reference to any government entity, activity, contract, test event, operational scenario, mission area, or public-sector organization shall be interpreted to imply sponsorship, approval, recommendation, certification, authorization, partnership status, or endorsement by the United States Government or any of its departments or agencies.
Department of Defense Visual Information Notice
“The appearance of U.S. Department of Defense visual information does not imply or constitute DoD endorsement.”
This statement is used consistent with publicly released Department of Defense visual information guidance. Where possible this statement will always be provided adjacent to the images of concern.
Government Imagery and Publicly Available Materials
Blueskytec America Inc. may reference or display publicly available government imagery, publicly released materials, historical references, publicly accessible technical information, or publicly distributed media for informational, educational, contextual, historical, interoperability, or illustrative purposes.
Use of such materials does not imply endorsement, sponsorship, approval, authorization, certification, or affiliation by any government agency or official.
Public-domain status of government-created materials does not authorize the implication of government endorsement.
Government Seals, Emblems, Insignia, and Logos
Official seals, emblems, insignia, logos, trademarks, service marks, and related identifiers of the United States Government, the Department of Defense, Military Services, federal agencies, and associated organizations remain the property of their respective owners.
Blueskytec America Inc. does not claim ownership of any government seal, insignia, logo, emblem, or trademark.
Many government seals, insignia, and official identifiers are restricted by law or policy and may not be reproduced or used for commercial purposes without authorization.
Where government names, insignia, or symbols appear on this website, they are used only for factual reference, identification, interoperability discussion, historical context, public-interest commentary, or other legally permissible purposes.
Marine Corps Specific Notice
Where applicable under 32 CFR § 765.14, the following notice applies:
“Neither the United States Marine Corps nor any other component of the Department of Defense has approved, endorsed, or authorized this product (or promotion, or service, or activity).”
Product, Capability, and Performance Statements
Statements regarding products, technologies, demonstrations, testing activities, operational relevance, compatibility, security capabilities, performance characteristics, technical approaches, or mission applicability reflect the views, engineering assessments, testing outcomes, operational observations, or business positions of Blueskytec America Inc. unless explicitly attributed otherwise.
Descriptions of prior testing, demonstrations, evaluations, prototypes, or integration activities do not imply operational deployment status, formal procurement approval, fielding decisions, certification authority decisions, future contract award, or endorsement by any government agency.
Third-Party Organizations and Trademarks
Any third-party company names, product names, trademarks, logos, service marks, agency names, military designations, command names, or organizational references appearing on this website remain the property of their respective owners.
Their appearance does not imply affiliation, sponsorship, endorsement, certification, interoperability approval, or partnership unless expressly stated.
Technical and Informational Content
Technical descriptions, white papers, diagrams, briefings, articles, presentations, demonstrations, and informational materials presented on this website are provided for general informational purposes only.
Operational suitability, deployment considerations, certification requirements, export restrictions, integration requirements, regulatory obligations, and security applicability may vary substantially by environment, mission profile, system architecture, classification level, and operational authority.
Organizations are responsible for conducting their own engineering, legal, operational, security, procurement, export-control, and compliance reviews before adopting or relying upon any technology or approach described on this website.
No Waiver of Rights
Nothing contained on this website shall be interpreted as granting any license, waiver, authorization, consent, or right with respect to any intellectual property, government mark, restricted identifier, classified information, export-controlled information, or regulated technical data.
All rights not expressly granted are reserved by their respective owners.
Contact
Questions regarding this notice or requests concerning attribution, imagery, trademarks, or referenced materials may be directed to Blueskytec America Inc. through the contact information provided on this website.