Before
A security or application team member would likely configure the scan, launch it, and return periodically to check whether it had finished. They would then export the results as a PDF, locate the correct SharePoint storage location, upload the file, and manually send the report link to the requester.
How it works
- Receive the requested web application URL and identify the requesting user.
- Create and launch the appropriate on-demand PCI web application scan, then monitor both the scan and PDF export until they are complete.
- Upload the dated PDF report to SharePoint and send its link back to the requester.
Workflow details
- Request intake: A secure webhook receives a command from a communication tool with the target web application URL and requesting user information. The workflow uses the user context to identify where to send the completed report.
- Scan preparation and execution: The automation retrieves the applicable scan template and user details, creates an on-demand web application scan configuration, and launches the scan against the supplied target URL.
- Automated monitoring and reporting: It checks the scan status at regular intervals until completion, starts a PDF export, monitors the export operation until it is ready, and downloads the finished report.
- Storage and notification: The workflow locates the designated SharePoint site and drive, uploads the report with a date-based filename, and sends the requesting user a message containing the report link and filename for review or further analysis.
What changed
The request-to-report handoff is now automated from a single webhook command. Scan execution, completion checks, PDF preparation, SharePoint storage, and requester notification occur in sequence without repeated manual status checks or cross-tool copying, while the recipient can still review the resulting report.
Work removed
Creating scan configurations, selecting scan templates, launching scans, checking scan and export statuses, downloading PDF reports, locating the SharePoint site and drive, naming and uploading files, and manually sending report links to requesters.
Expected outcome
Each request can remove approximately nine recurring manual actions across scan setup, monitoring, reporting, storage, and notification; this is a workflow-based estimate rather than a measured customer result.
