Your attack surface has blind spots. Find them before someone else does.

Skyreach Orion brings your clouds, tools and networks into one model and shows you what an attacker could reach. Run it on your own infrastructure, with engineers who tailor it to you.

Request a demo See how it works
  • Microsoft Azure
  • Amazon Web Services
  • Google Cloud
  • On-Premises

Plus common network and security appliances. Our engineers connect anything else you run.

Scattered security data brought into one model Data from AWS, Azure, Google Cloud, firewalls, identity, VM disks, cloud storage and other tools flows into Skyreach Orion, which connects it into one graph and highlights a public path from the internet to the prod-db database. AWS Azure Google Cloud Firewalls Entra ID VM disks Cloud storage Your tools Skyreach Orion Internet Load balancer web-01 app-identity prod-db backups Blind spot: public path to prod-db

"Are we exposed?" shouldn't take three weeks to answer

Skyreach Orion loads data from any source into a security ontology: a shared map of your resources, identities, networks and findings, and how they connect. Every product and dashboard reads from it.

How data flows through Skyreach Orion Sources such as AWS, Azure, Google Cloud, on-premises networks and your own tools send records to the integration bridge, which stores them as received. A versioned mapping, which AI can draft for review, turns them into the security ontology of 77 entity types and 56 relationship types. Modules such as exposure management and PQC discovery read from that ontology. Your sources Integration bridge Mapping Security ontology Modules AWS Azure Google Cloud On-premises Your own tools Stored as received source: aws.ec2 type: VirtualMachine links: in: Subnet uses: NetworkCard AI-assisted draft You review, then activate 77 entity types 56 relationship types Exposure management PQC discovery Your own dashboards How data flows through Skyreach Orion Sources such as AWS, Azure, Google Cloud, on-premises networks and your own tools send records to the integration bridge, which stores them as received. A versioned mapping, which AI can draft for review, turns them into the security ontology of 77 entity types and 56 relationship types. Modules such as exposure management and PQC discovery read from that ontology. Your sources AWS Azure Google Cloud On-premises Your own tools Integration bridge Stored as received Mapping source: aws.ec2 type: VirtualMachine in: Subnet AI-assisted draft You review it Security ontology 77 entity types 56 relationship types Modules Exposure management PQC discovery Your own dashboards

  1. Integration bridge

    Connectors send records exactly as each source provides them. They are stored as received, so nothing is lost and data can be remapped later without collecting it again.

  2. Mapping

    A versioned mapping turns each record into ontology types. AI can draft a mapping from sample records, and your team reviews it before it goes live.

  3. Security ontology

    77 entity types and 56 relationship types, from virtual machines to identities to firewall rules. Add types of your own without changing the core.

Built to be trusted with your most sensitive data

A tool that maps every weakness you have is a target in its own right. So we built Orion to stay under your control, to grow without a per-asset bill, and to fit the way you work.

Your data stays yours

Your security data is the map an attacker wants. Self-host Orion in your own environment and nothing leaves it. You choose where the data lives and who can reach it.

No bill for every new asset

Most platforms charge per asset, so teams leave things out of scope to save money, and those become the blind spots. We don't count your assets. Connect everything.

Engineers alongside your team

You don't get a login and a manual. Our forward-deployed engineers connect your tools, map your data and build the detectors and dashboards you need.

If you run it, we can connect it

Install connectors and detector packages from the marketplace, or have us build one for an internal or niche tool. It becomes a package you keep, private to your organisation.

Start with what worries you most

Turn on the products you need. Each one reads from the same model, so findings link up across them.

An attack path from the internet to a database An attack path in five hops: from the internet, through a network security group with SSH open to everyone, to web-01 running a vulnerable OpenSSH version, to an identity that can read Key Vault secrets, ending at prod-db, which holds customer data. Internet Entry point nsg-frontend Network security group SSH open to 0.0.0.0/0 web-01 Virtual machine Vulnerable OpenSSH version app-identity Managed identity Can read Key Vault secrets prod-db SQL database Holds customer data

Exposure management

Find the exposure that matters, ranked by what an attacker could actually reach.

  • Cloud security posture: 1,900+ detectors across AWS, Azure and Google Cloud
  • Attack paths across network, identity and data access
  • Identity and access analysis, including privilege escalation
  • Internet exposure and secrets in cloud storage
  • Software inventory and vulnerabilities (SBOM)
See attack path analysis
Cryptographic asset inventory An inventory of 47 cryptographic assets found on VM disks and in cloud TLS policies: 6 are weak today, such as an RSA-1024 deploy key and a SHA-1 signed VPN certificate, and 41 are quantum-vulnerable, such as RSA-2048, ECDSA P-256 and Ed25519 keys. 47 cryptographic assets found 6 weak today 41 quantum-vulnerable api.internal RSA-2048, on web-01 Quantum-vulnerable deploy key RSA-1024, on build-02 Weak today partner-sftp ECDSA P-256, on sftp-01 Quantum-vulnerable legacy-vpn SHA-1 signature, on gw-01 Weak today SSH host key Ed25519, on bastion Quantum-vulnerable Found on VM disks and in cloud TLS policies

PQC discovery

Find the cryptography that quantum computers will break, and the cryptography that is weak already.

  • Certificates and SSH keys found on VM disks
  • Cloud TLS policies checked for post-quantum support
  • Weak and quantum-vulnerable algorithms flagged
  • Keys matched to the servers they can log in to
Ask about PQC discovery

The questions your security team will ask

Where it runs, what we access and how we charge. Anything else, ask us.

Can we host Skyreach Orion ourselves?

Yes. You can run Orion in your own environment, so your security data never leaves infrastructure you control. We can also host it for you.

How is Skyreach Orion priced?

We don't charge per asset, so connecting another account or workload doesn't add to your bill. Plans depend on the products and engineering support you need. Ask us for a quote.

What access does Skyreach Orion need to my cloud accounts?

Read-only access. In Azure and AWS the base role can read resource metadata but has no write or delete permissions on the environments you connect.

Optional features, such as scanning VM disks for installed packages, need extra, narrowly scoped permissions. They are off unless you turn them on.

What data do you collect?

Configuration metadata: resources, network rules, identity and access policies, and how they relate. We use it to build an inventory graph of your environment. We do not copy the data held in your applications or databases.

How are our credentials protected?

Credentials are stored encrypted and handed to a collector only while it runs. For Azure we use certificate-based authentication, so no passwords or client secrets are stored.

Do we need to open inbound firewall ports?

No. Connections are outbound only, so there are no inbound firewall changes to make.

What if a tool we use is not supported?

Our engineers work with your team to connect it. Internal platforms and niche security tools are mapped into the same model as everything else.

How current is the data?

Sources sync on a schedule, as often as every 15 minutes. Anything that disappears from a source is removed from the model on the next sync.

Find out what you can't see

Request a demo. Tell us about your environment and we reply within one business day.

What happens next

  1. We review your environment details
  2. We schedule a 30-minute technical call
  3. We prepare an evaluation plan for your environment

We use these details only to reply to your request. See our privacy policy.