Security
Built for data that has to be protected.
Lynx holds personal, financial and security data, so it was designed for Impact Level 5 from the start. Companies get the same controls in their own cloud or Microsoft tenant. Here is what the platform does today.
Sign-in
- The U.S. Government information system notice first, as a popup only OK closes; every sign-in route refuses until it is acknowledged
- Your security protocol, with multi-factor authentication required in the token
- CAC/PIV: the certificate chain checked to the DoD CAs, its dates and revocation, and the EDIPI matched to the person
- Password with an authenticator code only for people an administrator allows; lockout after five failures
- 15-minute idle timeout and 8-hour session limit
Access
- Security roles open features and carry None, Read or Edit per area; directory groups can carry roles
- Supervisors, alternates and Admin Officers see only their own people and offices
- Personal and security fields locked; the values never reach the browser of anyone without the role
- Module access allowed or denied per person; refusals are audited
- Two-person rule for administrator rights; nobody changes their own roles
- Access reviews, sign-in history, break-glass accounts and inactive account review
Audit and records
- Append-only, hash-chained audit log of every sign-in, refusal and change, with what it was before
- The chain verified on demand; the log searched and exported
- Records retention on the General Records Schedule, with legal holds and approved disposal only
- Security records kept as status and dates only; never investigation content or anything classified
Hosting
- Built to run in government clouds at Impact Level 5
- Hosted on Azure, AWS or Google Cloud with a PostgreSQL or SQL Server data tier, so it is not tied to one cloud
- Nothing loaded from outside the application at run time: no CDNs, web fonts or analytics; runs with no internet egress
- Strict Content Security Policy, no-store caching and marking banners on every page and export
- Secrets in your cloud’s key vault; credentials for connectors held by name, never stored in the database
AI
- Models run behind a provider interface inside your boundary; the approved model is a configuration choice
- The Assistant answers only from data the person may already see
- A classified record is never sent to a model
- System prompts change only with a second person’s approval
Files and evidence
- Uploaded documents declare Unclassified or CUI; anything with a classified marking is refused and the Security Manager alerted
- Files open only after a malware scan, and every open is audited
Authorization
Supporting your ATO.
Lynx is built to run in a Government-provided Impact Level 5 environment and to map to the controls government clouds require, to reduce the time and effort of your Risk Management Framework (RMF) process. Lynx does not currently hold a FedRAMP authorization or an agency Authority to Operate (ATO). We support your ATO with architecture, SBOM, vulnerability scanning and configuration documentation, and work alongside your security team when we deploy Lynx in your cloud or tenant.
With the Power Platform option, Lynx runs inside your own Microsoft tenant, on the Microsoft cloud your tenant already uses (such as GCC or GCC High), under your Power Platform governance and data loss prevention policies.
Report a vulnerability to security@hyertek.com.
Take Lynx through your security review.
We’ll send the architecture overview, SBOM and scan summary, and walk your security team through the controls.