WhiteHat Sentinel/Source Connectors

The WhiteHat application security tools combine automation, artificial intelligence technology, and human intelligence to deliver application security at scale. WhiteHat offers a number of products including DAST, SAST, and SCA scanning tools.

 

Kenna.AppSec users can use the WhiteHat Sentinel or Source Connectors to import your application scan information from the two products into Kenna to assist you in reducing risk across your applications.

 

User Prerequisites/Connector Setup:

Given that WhiteHat is deployed in the cloud, the connector has the following requirements:

  • Have API access to WhiteHat

  • be a Kenna Administrator to configure the connector

Configuring your WhiteHat Connector in Kenna

To import your data from WhiteHat Sentinel/Source to the Kenna.AppSec module, users can leverage the WhiteHat Sentinel Connector in the Dynamic Assessment category, or WhiteHat Source in the Static Assessment Category.

If you are using Sentinel, navigate to the Dynamic Assessment section in the Connectors tab in your Kenna deployment and select WhiteHat Sentinel or if you are using Source, navigate to the Static Assessment section and select WhiteHat Source as shown in the screenshot below.

 

lmn.png

After you select the Connector, on the new screen that displays, complete the following fields:

  • Enter a name for the connector or you can leave the default name - Sentinel or Source, if you wish.

  • Enter your WhiteHat API Key

  • Since WhiteHat has a standard location for data retrieval, there is no need to enter any custom URL or host information to access your scans.

  • Select the frequency that you want to run your Kenna WhiteHat Connector

Tip: It is recommended you run the connector in conjunction with how often you run the WhiteHat scan(s).

  • If you would like to set a connector-level asset inactivity limit, you can do that at this time, or later. Refer to Setting Asset Inactivity Limits for more information.

Help: To retrieve the API Key, login to your WhiteHat account and navigate to your profile page and you will see a link for the API key.  The screenshot below shows the popup message you will see when displaying your API key.

WhiteHat_Sentinel_and_Risk_Meter_2_0_Customer_Notification.png

 

Which WhiteHat Sentinel Items Does Kenna Import?

Kenna imports all of the applications associated with the user leveraged for the connector. We pull:

  • Applications

  • Assets

  • Findings/Vulnerabilities

    • Descriptions & Custom Descriptions (Sentinel)

    • Solutions & Custom Solutions (Sentinel)

    • Diagnosis and Solution (Source)

  • Tags

  • Associated Dates

What API Calls Are Involved?

  • https://sentinel.whitehatsec.com/api

    • source_vulns, vulns

    • assets

    • sites

What WhiteHat Items Are Turned into Kenna Tags?

  • Tags

  • Site ID

  • Labels

  • Asset Owner Name

  • Custom Asset IDs



Optional Settings

The following settings can be enabled on the back end for both WhiteHat Connectors.

Important: To have these settings enabled, or for more information, contact your Customer Experience (CX) Team.

  • Exclude Informationals

    • When this option is enabled, Kenna does not import vulnerabilities that do not include a CVE, CWE, or WASC ID.

  • Skip Tags

    • This setting allows you to NOT create any tags within Kenna based on the WhiteHat metadata.

  • Ignore Scanner Last Seen Time

    • If you do not want the asset last seen time in Kenna to be the scanner reported last seen time.

  • Tag Reset

    • This setting assists in keeping your WhiteHat metadata in sync with Kenna. Each time the connector is run, ALL tags within Kenna are removed and the WhiteHat tag metadata is re-created.

    • If you have created any manual tags OR any tags were created off of metadata from other connectors, that tag info is removed and is refreshed once those other connectors are rerun.

  • Custom Ordered Locators

    • Locators (IP, Netbios, FQDN, etc) can be reordered to better deduplicate vulnerabilities on the Connector level or the entire Platform level. For more information, refer to this help article.

Common Reasons for WhiteHat Connector Run Failures

  • Bad Credentials

    • If you enter the incorrect API Key during the connector setup, we will not have access to the WhiteHat environment to make the API calls.

  • If an API call fails (no data available, or other reasons)

  • Unexpected data returned

    • If Kenna receives data that is not in the expected format and we are unable to process it, the connector will fail.

  • If more than 1% of connector payloads fail to import as expected, we will auto-fail the Connector Run.

Additional Assistance:

Please contact Kenna Support should you require any additional assistance with the WhiteHat Sentinel Connector.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.