What's new in Lyrie Hex — v1.2
What's new in Lyrie Hex — v1.2
This update is focused on three things our customers told us mattered most: audit-ready compliance output, broader coverage on every scan, and even higher precision in your reports. Everything below is live right now — no action needed on your side.
At a glance
- Compliance reports — download PCI DSS 4.0, HIPAA, SOC 2, ISO 27001, and FedRAMP Moderate reports from any completed scan.
- Expanded scan coverage — fifty-plus new built-in checks across application, identity, infrastructure, real-time, and configuration surfaces.
- Verified exploit chains — when two related issues line up, your report shows the end-to-end confirmed attack path, not just the parts.
- Sharper detections — dozens of false-positive sources retired this release. Your reports are tighter and faster to act on.
- Faster results — backend improvements deliver scan results sooner, with steadier performance under load.
Compliance reports — five frameworks
Every completed scan can now produce compliance reports for the standards your auditors actually ask for:
- PCI DSS 4.0
- HIPAA Security Rule
- SOC 2 (Trust Services Criteria)
- ISO 27001:2022
- FedRAMP Moderate (NIST 800-53 Rev. 5)
Each report shows every relevant control with a clear PASS / FAIL status and links straight to the findings that drove the result. Available as Markdown and HTML — ready to hand off to auditors, security committees, or your GRC pipeline.
You'll find the new download options on every scan's report page in your dashboard.
Broader built-in coverage
Lyrie now runs fifty-plus additional checks on every scan, covering infrastructure and application surfaces that previously needed bespoke configuration:
- Application surfaces — publicly exposed interfaces, service discovery endpoints, integration layers, and developer tooling exposure.
- Identity & access — authentication flows, token handling, authorization boundaries, and access-control validation.
- Cloud & infrastructure — sensitive deployment artifacts, credential exposure risks, environment configuration leakage, and infrastructure metadata access paths.
- Real-time systems — persistent connection frameworks, event-driven services, and message transport layers.
- Legacy integrations — older enterprise service interfaces and compatibility endpoints still commonly exposed in production environments.
- Server & platform configuration — debug interfaces, administrative utilities, monitoring surfaces, diagnostic pages, and unintended public assets.
Every new check is tuned for production targets — no extra noise from single-page apps, CDNs, or edge-WAF rewrites.
Verified exploit chains in your reports
When Lyrie spots two issues that combine into a real attack, it now confirms the chain end-to-end before flagging it. Your report includes a clearly labeled "verified chain" finding with redacted proof of execution. Initial coverage includes:
- Server-side request issues leading to infrastructure credential exposure
- Local file access leading to sensitive secret recovery
- Template injection leading to confirmed code execution
- Redirect handling flaws leading to authentication-flow compromise
This means the chains in your report are not theoretical — they ran successfully against your target.
Sharper detections, less review work
We made a substantial round of accuracy improvements this release. Detections are now stricter about what counts as evidence: every finding requires a specific structural signal, and most checks compare against a per-target baseline before they emit. The result is reports that are quicker to triage and easier to trust.
Faster, steadier scans
Behind the scenes, scans now run on a more resilient backend. Customers should notice quicker results during peak hours and steadier performance on long-running scans.
Nothing to do on your side
This update is fully rolled out across Lyrie. No settings to toggle, no migrations, no breaking changes — your dashboard, scan IDs, and existing report links continue to work exactly as before.
Questions or feedback? Reach us at [email protected].