Skip to main content

FAQ

1. How does Cyprob EE reduce false positives?​

Cyprob EE prioritizes evidence-backed findings and service-context-aware selection instead of running every check everywhere. In practice, this reduces analyst noise and shortens validation loops.

2. Is Cyprob EE usable in air-gapped environments?​

Partly. The CVE database can be imported from an offline file (cyprob cve import). Plugin feed and appliance updates need network access to updates.cyprob.io or a mirror.

3. Can it scale without redesigning the platform?​

Cyprob EE ships as a single appliance VM that runs the server and its scan worker together. Scans are split into tasks that the worker takes from a shared queue. Contact us to size the appliance for larger estates.

4. Is installation complex for first-time evaluation?​

For POC/demo, it is designed to be straightforward with a guided setup path. Production deployments require standard infrastructure controls (networking, secrets, backup, operational ownership).

5. Do you support multi-tenant operations?​

Yes. The platform model includes organization-scoped operations, role-based access controls, and auditability expectations for enterprise and MSSP use.

6. What authentication and session controls exist?​

Login, refresh, logout, and session lifecycle endpoints are available. Production hardening should enforce strong credential policy, token/session governance, and access reviews.

7. How are secrets managed?​

Stored secrets (scan credentials, the SMTP password) are encrypted with AES-256-GCM under a key file that the appliance creates on first boot and keeps outside the database (/var/lib/cyprob/secrets.key). Protect that file with the appliance's backup and access controls.

8. Does Cyprob EE currently execute Wasm plugins in production path?​

Yes. Plugins run in several formats: YAML, HTTP/SSL templates, converted Nuclei templates and WebAssembly (Wasm) modules. Wasm modules run in a wazero sandbox with host-enforced time and memory limits. Customer-written Wasm plugins are not supported.

9. What happens if license expires?​

Operational policy should follow your licensing agreement. After expiry the appliance keeps working for a 15-day grace period, then switches to read-only. Data stays readable; scans and changes are refused until a new license is applied.

10. What is the best POC success criterion?​

One repeatable scan-to-report cycle with defensible findings, validated by both security and infrastructure stakeholders, plus a clear production rollout recommendation.

Next Action​

If objections are resolved, proceed to production planning with ownership mapping and phased rollout scope.