FedCatalog

xDome for Government

Claroty

Claroty’s xDome for Government is a SaaS-based Cyber Physical Security (CPS) FedRAMP High Cloud Service Offering (CSO) that enables security outcomes for…

In processHighNo agency authorizations on record
FedRAMPIn processAgency path ⓘ
FedRAMP impact levelHighGovernment Community Cloud
Runs on—Not recorded by FedRAMP
Agency authorizations0ATO or reuse on record ⓘ

Source: FedRAMP Marketplace · refreshed Oct 7, 2026 · How the data works

How to buy

Confirmed paths come from GSA and the FedRAMP record; searches are places to look.

Confirmed buying paths

  • Vendor directGovernment sales page from the FedRAMP record
    Visit →

Other places to check

✓ verified by FedCatalog · ○ vendor-supplied and reviewed · searches are places to look, not matches. FedCatalog shows what it can verify and labels what it can’t. Sell this to government? Send exact marketplace, GSA or SEWP listings to mark@fedcatalog.com.

FedRAMP Marketplace listing ↗ · Section 508 ACR Repository ↗ · SAM.gov ↗

What it does

Claroty’s xDome for Government is a SaaS-based Cyber Physical Security (CPS) FedRAMP High Cloud Service Offering (CSO) that enables security outcomes for visibility across diverse IOT/OT use cases, vulnerability management, exposure management, as well as threat detection, and asset purpose and efficiency.

Authorization details

  • Offering
    xDome for GovernmentFedRAMP ID FR2323961436
  • Status
    Agency In ProcessAgency authorization path
  • FedRAMP impact level
    HighAuthorized against the FedRAMP High baseline, the most extensive control set.
  • Deployment
    Government Community CloudSaaS
  • Runs on
    Not recorded
  • Assessor (3PAO)
    Fortreum, LLC
  • Government sales
    sales@clarotygov.usContact published on the FedRAMP listing
  • Data as of
    Oct 7, 2026FedRAMP Marketplace, refreshed daily

An authorization belongs to this specific offering and boundary; the vendor’s other offerings are listed separately. Source: FedRAMP Marketplace · refreshed Oct 7, 2026.

Something wrong or missing on this page? Email me and I’ll fix it by checking the source.