Your data stays on your servers
Stratholt™ runs on one server inside your network, behind your sign-in. It talks only to systems you set up, such as your SIEM and sign-in proxy, and we never need to see your data.
The short version
- Runs onOne Windows or Linux server
- NetworkOnly systems you set up
- Data inFiles your team exports
- Sign-inYour single sign-on, or local accounts
- AccessFour roles; CAMs change only their own accounts
- Export controlITAR programs open to US persons only
- LogsAdd-only, can go to your SIEM
- BackupsNightly and checked; optional encryption
- EncryptionYour server's FIPS 140-3 OpenSSL
- MarkingsYour notice and the CUI marking
- Runs on
- One Windows Server, or Linux with Docker. An offline installer for servers with no internet.
- Network
- No connections to us, and no outside internet calls except to systems you set up, such as your SIEM or sign-in proxy. It sits behind your own reverse proxy and certificate, and its pages load nothing from other sites.
- Data in
- Files your team exports from the ERP and scheduler, uploaded on screen or dropped in a folder on the server. No connection into SAP, Oracle or Cobra.
- Sign-in
- Your single sign-on through the proxy (Windows authentication, Entra ID, Okta or ADFS), or local accounts with an authenticator app. Lockout after failed attempts, and idle sign-out.
- Access
- Four roles: Admin, Program Control, Analyst and CAM. CAMs change only their own control accounts. Each person sees only the programs they're given.
- Export control
- A program marked ITAR opens only to accounts marked as US persons.
- Logs
- Security and decision logs that can only be added to, chained so any edit shows. Can be sent to your SIEM by syslog over TLS.
- Backups
- Nightly, checked after writing, one per program. Can be encrypted (AES-256-GCM).
- Encryption
- Uses the server's OpenSSL. Where that OpenSSL is a FIPS 140-3 validated module running in approved mode, Stratholt™'s encryption and hashing run through it.
- Markings
- Your approved notice before sign-in, and a CUI marking on every page, file and workbook.
How we set up, fix and update it without your data
Your data stays on your server the whole time. This is how support works around that.
Setup
We set it up with your team, in your own copy of Stratholt™: the setup questions, your company's terms, and an import recipe for each report. Your differences become settings, not custom code.
A report that won't read
You send its header row, or a sample made on your machine with the built-in scrubber: same layout, made-up values. Only with your agreement.
Bugs
Most are reproduced on our side with the demo program. If we need more, your admin makes a diagnostic file: versions, settings with secrets removed, and counts. No cost lines, amounts, part numbers or employee data. You read it before you send it.
Updates
Fixes and new features arrive as a new release. Your IT installs it; the installer backs up first and keeps your data and settings.
What ongoing support doesn't need
- Remote desktop or VPN access to your server
- Copies of your ERP extracts, backups or databases
- A standing account for us on your system
For your ISSO
The documents an ISSO or assessor asks for, written for the server that hosts Stratholt™. Ask for them with a demo.
- NIST SP 800-171 responsibility matrix. All 110 requirements: what Stratholt™ provides, what's shared and what stays with you. CSV and OSCAL, with a Rev 3 crosswalk.
- Hardening guide and CUI deployment checklist, each item tied to the 800-171 requirement it supports.
- FIPS 140-3 statement. Exactly what is encrypted, how, and through which module.
- Application security STIG self-check. Our own assessment, to start your review.
- Secure development practices (NIST SSDF).
- Penetration test scope, ready to hand to an independent tester.
- Support model: how support works without access to CUI.
Stratholt™ doesn't make a system 800-171 or CMMC compliant on its own. It gives your security team what they need to assess the server it runs on.