Hypersync workflow
Linking proof to controls in Hyperproof is a key part of compliance operations. This typically takes the form of files and documents such as data log files, screenshots, meeting notes, etc. Without Hyperproof, users must manually link the proof they collect to the appropriate controls in their framework(s).
A typical workflow for collecting proof without the use of Hypersyncs may look like:
Compliance manager creates a request for someone—typically an IT admin—to obtain proof from an application, e.g. a list of critical vulnerabilities detected in the last 30 days and the mitigation status.
Compliance manager waits for IT admin or relevant individual to obtain proof and send it to them.
Compliance manager or IT admin manually uploads the files to Hyperproof and then links them to the appropriate controls.
Hypersyncs automate this process and eliminate the need for manually linking proof.
The workflow for Hypersync users after the Hypersync is connected and created:
Proof is automatically generated via a PDF or a spreadsheet and linked to relevant controls and/or labels.
Nothing else. That's it!