Skip to main content

What does Hypersync proof look like?

Hyperproof can automatically generate evidence from a variety of cloud-based apps and services via Hypersyncs. This saves time, avoids the typical hassles of manually tracking down information, and ensures data is accurate, complete, and up-to-date, since it comes directly from the source.

What is a Hypersync?

A Hypersync is an automated API call to an online service that returns evidence specifically designed to support various compliance scenarios. Hypersyncs automate evidence collection for items such as password settings, backup settings, encryption settings, access groups, user lists, code change evidence, and more. Hypersyncs are configured to run on a user-selected schedule, so there is no ongoing interaction required to keep the proof up to date.

What does the proof look like?

Hyperproof transforms data pulled from the host system into a format that is both human and machine-readable. The latter is important for enabling Hyperproof’s automated control testing feature.

Proof automatically collected by a Hypersync can vary slightly in appearance, but there are some common areas. Every piece of proof created by a Hypersync contains three sections: the header, the body of the proof, and the footer.

Note: The date format for dates in proof types generated by Hypersyncs is determined by the locale of the time zone set for the organization in Settings > General.

Every piece of proof uploaded in Hyperproof contains the following metadata:

  • File name and type (e.g., image)

  • File size

  • Version (if applicable)

  • Owner of the file

  • Name of the individual who uploaded the file. If uploaded by a Hypersync, the individual is always System User.

  • When the file was uploaded

  • When the file was created

  • How the file was uploaded (e.g., via a Hypersync)

  • Linked controls

Breaking it down

Here we’ll take a closer look at the three sections that make up a piece of collected proof. Below is an example of a Datadog proof type in PDF format.

Header

The header tells you what data appears in the body of the proof: the source app, the proof type, and any criteria specified when you created the Hypersync.


hypersync-header.png


Body

The body of the proof shows the data collected by the Hypersync. The exact format of this section varies depending on the app and proof type. The most common format is a table.

hypersync-body.png


Footer

The footer shows how Hyperproof collected the data, specifically:

  • When the data was collected

  • The user account used to collect the data and how Hyperproof connected to the source app

  • A link to see the same information in the source app console used for observation testing to verify that the data shown in the automated evidence document matches the source system. Some audit/assessor firms perform observation testing on a sample of Hypersync evidence to gain assurance that the evidence is pulled accurately and completely. Note that the user who clicks the link needs access to the source system.

  • Detailed information on the SDK or API and parameters used to generate the data

hypersync-footer.png


​Where can I view the proof?

Hypersync proof appears in the proof grid with all of your other proof. You can identify proof created by a Hypersync by its source app icon and its health indicator.

view-proof-2.png

Tip: To view all proof linked to Hypersyncs, look for the source app's icon. Additionally, click the icon to access the Hypersync's settings.

Did this answer your question?