Start with thirty minutes

User guide

The product's own user guide. Every screen shows Aldervane Health, a fictional organization. All data is synthetic.

Ciphren user guide

Ciphren shows an organization what the outside world can see of it. That means the systems it exposes to the internet, the weaknesses on them, the suppliers it depends on, and the threats aimed at organizations like it. Then it helps you decide what to do first.

Most security tools look from the inside out: agents on laptops, logs from firewalls. Ciphren looks from the outside in, the way an attacker, a regulator or a journalist would. That view is unfamiliar at first, and it can feel like a lot. This guide explains what each page shows and, more importantly, why it matters and what to do about it.

The organization in this guide

Every screenshot shows Aldervane Health, a regional health system with hospitals, clinics, a foundation and six key suppliers. Aldervane is fictional. So are its people, suppliers and web addresses, and every screenshot is marked demonstration · synthetic data across its top. What's real is what you'd check: the software, its published vulnerabilities, their severity scores, and whether the U.S. government lists them as exploited in the wild.

Chapters

  1. What Ciphren is: the outside-in view, and where the data comes from
  2. Start with the Executive Brief: your posture in one page, and the decisions it asks for
  3. A walkthrough: from a news story to your own server: how the pieces connect
  4. Findings: every weakness found, and how to work through them
  5. Locations: which hospital, campus or office a finding belongs to
  6. Vendors: the suppliers you depend on, and how exposed they are
  7. Incidents and narratives: what's happening around you
  8. Infrastructure: your hosts, domains, certificates and email defences
  9. Entities and the intelligence wiki: the people, organizations and systems in the picture
  10. Asking questions: search, Ask, Deep Reasoning and threat models
  11. Reports: the weekly briefing
  12. For administrators: invitations, access levels, MFA and the audit log
  13. Glossary: every term in plain language
  14. Questions security teams ask: the collection, findings, your data, and connecting other tools

If you read only one chapter, read chapter 2. If you read two, add chapter 3.

Start with thirty minutes