Skip to main content

Wallarm proof types and permissions

Written by Hyperproof Support
Updated over 3 weeks ago

πŸ“ Note

Hyperproof connects to many third-party systems that frequently change, including the system interface. Contact your System Administrator or the third-party provider for assistance in meeting the requirements to integrate with Hyperproof and collect the proof you need.


Hyperproof supports collecting proof from Wallarm.
​

When you create a Hypersync between Hyperproof and Wallarm, you can automatically collect the following proof types:

Wallarm proof types and fields

Proof type

Fields

Testable

Scanner State

Org, LastScanTime, LastVulnTime, LastScanDur, LastVulnDur, NextScanTime, NextVulnTime, ScanLevel Stat

Yes

User List

User Id, User Name, Full Name, Email Address, Enabled, Permissions, Last Login

Yes


​

This Hypersync supports importing a user list for an access review. See Importing a list of application users with a Hypersync for more information.

Requirements

To connect to Wallarm and collect proof your Wallarm configuration must meet the following requirements:

  • An administrator on Wallarm must create an API token for use by Hyperproof. From the Wallarm Console β†’ Settings β†’ API tokens. The minimum permissions for the API token must be Source Role = Custom with View on all resources.

Connection configuration

Authentication type: Custom
​

Custom authentication parameters: Cloud Instance, API Token

When you configure the Hypersync for Wallarm the first time you must provide the following information:

  • Cloud Instance - select the instance where your Wallarm account resides - US Cloud or EU Cloud

  • API Token - enter the API Token that Hyperproof should use to access Wallarm


πŸ“ Note

You only need to connect Hyperproof to the app once, and then you can create as many Hypersyncs as you need.
​

Additionally, you can create multiple Hypersyncs for a single control or label.


Additional documentation

Did this answer your question?