Reporting
Reporting and data export
Cyprob produces every report inside your own environment. The underlying scan data stays on your servers.
Which report for whom
A security team needs the detail behind each finding, while management usually asks for the trend over the last quarter and an auditor asks for the evidence behind a closed item. The reporting screen builds all of these outputs from the same data. Periodic reports can be scheduled, so the file is already prepared when the audit period arrives.
How data reaches other systems
Findings and the asset inventory are read through a REST API. Your own team builds the connection to a SIEM, a ticketing system or a data warehouse, so you decide which system receives the data, in what format and how much of it. Nothing is exported by the product on its own.
Common questions
What does the auditor get?
Evidence. Every finding is stored with the request that was sent and the response that came back, and the report is built from that record. The same data produces separate outputs for engineers, management and auditors.
Are reports produced by hand?
No, they are scheduled. Periodic reports are defined against your calendar and the output is ready when the period closes.
Does report data leave the environment?
No. Reports are produced inside and the raw data stays on your servers. Any export to other systems is built on your side over the REST API.