Questions
What organizations ask before they start
Straight answers to the questions we hear most. If yours isn't here, ask us.
What does Ciphren do?
We watch, we map, we brief. We collect what anyone outside can see about your organization, the third parties operating on your behalf, and the stories told about you. We keep it as one current map. Then we brief you on what changed and what to decide.
How is this different from the security tools we already run?
Most security tools watch what you operate, from the inside. We watch everything you answer for, from the outside. That includes systems your vendors run for you, and the stories told about you. We add to the tools and feeds you already have. We don't replace them.
Where does the information come from?
Public sources only. We read what your public-facing systems show any visitor, the public record, the press, and public posts. Every item is traced to its source and dated.
Do you touch our systems?
No. Every request is an unauthenticated read: the page requests a browser makes. We never sign in, never test a credential, and never confirm a weakness by triggering it. Requests are paced so they never burden or disrupt a service. There is nothing to install and nothing to connect.
What do you need from us to start?
A conversation. Together we agree what to watch: your organization, the units you answer for, your key vendors, and the questions you care about most. Your picture builds from the first collection. Its history starts with the second.
What can't you see?
Anything that isn't public. We don't see inside your network, your email, or your private systems. The security tools you already run do, which is why we work alongside them. A finding shows what a system tells the internet. It is not proof of a breach.
What do we receive, and how often?
A brief written for the person who answers for the organization, with the full picture behind it in the portal. Collection typically runs weekly, and your plan sets the pace. We check the news more often, so a story about you usually reaches your picture within a day.
Can we ask it our own questions?
Yes. Ask in plain language for a report, a threat model, a dependency map, or a search across everything on record. Every answer cites the records behind it, so you can check it.
Does it work with the tools we already use?
Yes. Your team can pull the data into its own tools through an API, and connect the AI assistants it already uses. The details are in the security packet.
Does Ciphren use AI?
Yes. It's how the work gets done at this speed. The findings themselves come from fixed, repeatable checks, not from AI. AI then reads across them to write the brief and answer your questions. It works only from what we've collected, and it cites what it uses. People calibrate every instance, and can override or retract a mistake.
How accurate is it?
Every finding rests on an observation you can open and check: what was seen, where, and when. Most findings are strong evidence rather than proof, and we mark the ones we've confirmed. Version checks correct for backported fixes, so your team isn't chased for a weakness that's already patched. Ciphren counts a finding as fixed only when it sees an upgrade from the affected version. A finding that simply stops appearing is reported as "no longer observed, not verified". No system is free of mistakes. That's why every item is sourced and dated, and people correct what's wrong.
Do you take sides on the stories you track?
No. We are strictly nonpartisan. We follow how a story spreads and whom it targets. We never rule on whether it's true.
Who can see our information?
You decide. Each person sees only what their role and handling level allow, using the Traffic Light Protocol labels security teams already know. You can use your existing sign-on if you want it. Every login, search, view, print and export is recorded in a tamper-evident audit log.
Can we see the product before we talk?
Yes. The user guide shows every page of the product on a fictional organization, with synthetic data.
What does it cost?
Pricing is set by the size and scope of your organization. It's in the packet, with the security review, architecture, hosting and retention terms, and the pilot agreement.