stryqbyte
  • Home
  • Performance
  • Contact Us
    • Get in Touch
  • FAQs
  • Solutions
    • Compliance & IT
    • Engineering
    • Medical Imaging
    • Government
  • Legal
    • EULA
    • Privacy
    • Terms
  • More
    • Home
    • Performance
    • Contact Us
      • Get in Touch
    • FAQs
    • Solutions
      • Compliance & IT
      • Engineering
      • Medical Imaging
      • Government
    • Legal
      • EULA
      • Privacy
      • Terms
stryqbyte
  • Home
  • Performance
  • Contact Us
    • Get in Touch
  • FAQs
  • Solutions
    • Compliance & IT
    • Engineering
    • Medical Imaging
    • Government
  • Legal
    • EULA
    • Privacy
    • Terms

For IT administrators · ISSOs · assessors · deployment engineers

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. 

Contact Us

Compliance IT Solutions

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.

Data handling

Data handling

Data handling

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.

CMMC-on mode

Data handling

Data handling

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.

Important: CMMC certifies an organization’s information system — not a software product. Stryq provides controls that help satisfy specific requirements when deployed as documented.

Stryqbyte security and compliance highlights

Protect CUI in transit (SC-8)

Protect CUI in transit (SC-8)

Protect CUI in transit (SC-8)

TLS 1.3; optional AES-256-GCM

Cryptography (SC-13)

Protect CUI in transit (SC-8)

Protect CUI in transit (SC-8)

 NIST-approved via OS/.NET*

Session authenticity (SC-23)

Protect CUI in transit (SC-8)

Session authenticity (SC-23)

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.

Audit (AU-2, AU-3)

Device authentication (IA-2)

Session authenticity (SC-23)

Timestamped security and transfer events are critical components in achieving CMMC certification, ensuring proper data handling and meeting IT compliance requirements.

Device authentication (IA-2)

Device authentication (IA-2)

Device authentication (IA-2)

Pinned certificates; pairing workflow for CMMC certification in data handling and ensuring IT compliance.

* FIPS-validated module claims require a FIPS-mode host. See full CMMC / NIST SP 800-171 mapping PDF for Partial and Customer-owned items.

IT deployment summary

Deployment models

  • LAN / site-to-site — fixed IPs, pairing codes, optional Scan LAN
  • Internet + rendezvous — IT-hosted rendezvous (port 5055); Find online for roaming receivers
  • NAT traversal — optional STUN + TURN relay (port 5056); relay never sees file payloads


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.

Download PDF

Copyright © 2026 stryqbyte - All Rights Reserved.

  • FAQs

Powered by

This website uses cookies.

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.

Accept