IT & Compliance — technical reference for Stryq 2.3
Data handling, security controls, CMMC-on mode, and deployment summary for evaluators and security officers. Not legal advice; does not certify your organization. CMMC certifies your organization — not the software.
A desktop standard your users will actually follow — without multi-tenant SaaS file storage. Offline seat licensing is validated on the device; file payloads are not sent to Stryqbyte during transfers.
File payloads are transferred directly between authorized Windows endpoints and are not stored in a Stryqbyte cloud file service during normal operation, ensuring compliance with data handling standards. Offline seat licensing is validated on the device, meaning that routine transfers do not send file contents or conduct live license checks to Stryqbyte, further supporting your IT compliance needs. The optional rendezvous feature, which is off by default, only shares metadata to assist endpoints in locating each other; actual file payloads are not transmitted. Additionally, audit logs are retained locally according to your configuration and are exportable for review in SIEM or SSP processes, helping maintain accountability in relation to CMMC certification.
When CMMC-on mode is enabled, Stryq enhances data handling by requiring stronger settings, such as elevated key-derivation parameters, and logs transfer events suitable for deploy-as-documented workflows. This process reflects in-application policy enforcement related to IT compliance, rather than organizational certification.
TLS 1.3; optional AES-256-GCM
NIST-approved via OS/.NET*
SC-23; Certificate pinning is an important aspect of ensuring IT compliance, while optional mTLS can enhance data handling practices in the context of CMMC certification.
Timestamped security and transfer events are critical components in achieving CMMC certification, ensuring proper data handling and meeting IT compliance requirements.
Pinned certificates; pairing workflow for CMMC certification in data handling and ensuring IT compliance.
Deployment models
Configure once: listen port in config.json (installer seeds 51000); firewall UDP+TCP on listen port; receiver TLS certificate; offline seat license per machine; optional rendezvous, relay, CMMC-on mode. Rendezvous is off by default.
Upgrades replace binaries but do not overwrite existing ProgramData config, certificates, or licenses.
We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.