Government
Cyprob for government
Cyprob runs on the institution's own network. Scan data does not cross the institution's boundary, and the product keeps full function on networks with no route to the internet.
What local engineering means
Cyprob is engineered in Türkiye and deployed on your infrastructure, under your administrators. How the product works, where the data sits and where an update came from are questions you can answer from the code: the core is published under Apache-2.0 and can be read and checked. For institutions bound by the Saudi PDPL or the UAE data protection law, the data never leaves the jurisdiction it was collected in, because the deployment has nowhere else to send it.
Full function on a closed network
On government networks with no internet access the product works in full. Catalogue updates are carried in as signed packages, and content that fails signature verification is not installed. Scanning, reporting and the audit trail all operate without a single outbound connection.
A structure that follows the institution
Organizations and teams are set up to match how the institution is actually divided. Each unit sees its own assets and manages its own scans, while the centre keeps one view across all of them.
Common questions
Can we verify what the product does?
Yes. The core is open under Apache-2.0, so the code can be inspected and the claims checked. Every plugin and update is signed, and unverified content never runs.
Does it work with no route to the internet?
At full function. Catalog updates are carried in as signed packages and verified inside. Scanning, reporting and the audit trail work without a single outbound connection.
Does it fit the structure of a large institution?
Yes. Organisations and teams are set up to mirror your units. Each unit sees its own assets and runs its own scans, while the centre keeps the full picture.