WhiteHat
Visualize WhiteHat Security scans, vulnerabilities, and findings, map them to code repositories, projects, or applications, and monitor changes through queries and alerts.
- Installation guide
- WhiteHat data model
Installation
For this integration, you will need to create an API Token key within your Whitehat account. See their documentation for more information.
Configuration in JupiterOne
To install the Whitehat integration in JupiterOne, navigate to the Integrations tab in JupiterOne and select Whitehat. Click New Instance to begin configuring your integration.
Creating a configuration requires the following:
The Account Name used to identify the Whitehat account in JupiterOne. Ingested entities will have this value stored in
tag.AccountName
when theAccountName
toggle is enabled.Description to assist in identifying the integration instance, if desired.
Polling Interval that you feel is sufficient for your monitoring needs. You may leave this as
DISABLED
and manually execute the integration.Your Whitehat API Key generated for use with JupiterOne.
Click Create once all values are provided to finalize the integration.
Next steps
Now that your integration instance has been configured, it will begin running on the polling interval you provided, populating data within JupiterOne. Continue on to our Instance management guide to learn more about working with and editing integration instances.
Data Model
Entities
The following entities are created:
Resources | Entity _type | Entity _class |
---|---|---|
Account | whitehat_account | Account |
Appliance | whitehat_appliance | Gateway |
Application and Mobile Application | whitehat_application | Application |
Assessment | whitehat_assessment | Assessment |
Asset | whitehat_asset | Application |
Codebase | whitehat_codebase | CodeRepo |
Component | whitehat_component | CodeModule |
Endpoint | web_app_endpoint | ApplicationEndpoint |
Finding | whitehat_finding | Finding |
Group | whitehat_group | UserGroup |
Role | whitehat_role | AccessRole |
Scan Type | whitehat_scan | Service |
Site | web_app_domain | Application, Host |
User | whitehat_user | User |
Relationships
The following relationships are created:
Source Entity _type | Relationship _class | Target Entity _type |
---|---|---|
web_app_domain | HAS | web_app_endpoint |
web_app_domain | HAS | whitehat_assessment |
web_app_domain | HAS | whitehat_finding |
whitehat_account | HAS | whitehat_appliance |
whitehat_account | HAS | whitehat_asset |
whitehat_account | HAS | whitehat_group |
whitehat_account | HAS | whitehat_scan |
whitehat_account | HAS | whitehat_user |
whitehat_application | HAS | whitehat_assessment |
whitehat_application | HAS | whitehat_codebase |
whitehat_application | HAS | whitehat_component |
whitehat_application | HAS | whitehat_finding |
whitehat_assessment | IDENTIFIED | whitehat_finding |
whitehat_asset | HAS | web_app_domain |
whitehat_asset | HAS | whitehat_application |
whitehat_group | HAS | whitehat_user |
whitehat_scan | PERFORMED | whitehat_assessment |
whitehat_user | ASSIGNED | whitehat_role |
Mapped Relationships
The following mapped relationships are created:
Source Entity _type | Relationship _class | Target Entity _type | Direction |
---|---|---|---|
whitehat_component | HAS | *cve* | FORWARD |
whitehat_finding | EXPLOITS | *cwe* | FORWARD |