Which scanning engines does Patrowl support?

Patrowl supports multiple scanning engines each running on dedicated ports: Nmap (port 5001) for port scanning, SSLLabs (5004) for SSL analysis, Arachni (5005) for web application scanning, Owl DNS (5006) for DNS reconnaissance, VirusTotal (5007) for malware checks, URLVoid (5008) for URL reputation, Cortex (5009) for threat intelligence, and several others.

How do I retrieve vulnerability findings from a scan?

After starting a scan via POST /startscan, poll GET /status/{scanId} until the scan status shows completion. Then retrieve structured findings via GET /getfindings/{scanId}. Findings include severity level, affected target, description, and remediation guidance. Results can be cleaned after processing via GET /clean/{scanId}.

Can I stop a running scan?

Yes. Individual scans can be stopped via GET /stop/{scanId} using the scan ID returned when the scan was started. To stop all running scans on an engine, use GET /stopscans. Partially completed scans may still have findings available via the getfindings endpoint.

How do I start a security scan through Jentic?

Search Jentic for 'start a security vulnerability scan', load the operation schema for POST /startscan, and execute with target and scan configuration parameters. Jentic handles the engine routing and returns structured findings. Install with pip install jentic.

What is the difference between liveness and readiness endpoints?

GET /liveness confirms the engine process is running and responsive. GET /readiness confirms the engine is configured and capable of accepting new scan requests. An engine may be alive but not ready if it is still loading configuration or has reached maximum concurrent scan capacity.

Can I limit what my agent is allowed to do with the Patrowl Engines API?

Yes. Because you run Jentic One yourself, your own rules decide which Patrowl operations and credentials your agent can use. Since Patrowl puts the scan ID in the URL path, such as GET /getfindings/{scanId} and GET /status/{scanId}, you can pin an agent to a single scan so it only checks status and reads findings. Destructive operations like GET /stop/{scanId} or GET /clean/{scanId} stay out of reach unless you explicitly grant them.