Configuring the WhiteHat Sentinel JIRA® Plugin
After installing the WhiteHat Sentinel Plugin, new configuration options are added to the Manage apps page, as displayed below. Refreshing the Manage apps page may be necessary.
There are seven possible configurations displayed. For the Sentinel Plugin to function, the Global Settings, Workflow Settings, Sentinel Integration, and at least one asset type (DAST Settings, SAST Settings, API Settings, or MAST Settings) must be configured. |
-
Configure Global Settings: Configure the connections between the plugin and Sentinel. Also configure how basic issues will be handled.
-
Configure DAST Settings: Configure the interactions between the plugin and DAST Sentinel services.
-
Configure SAST Settings: Configure the SAST interactions between the plugin and SAST Sentinel services.
-
Configure API Settings: Configure the interactions between the plugin and the Sentinel API services.
-
Configure MAST Settings: Configure the interactions between the plugin and MAST Sentinel services.
-
Configure Workflow Settings: Configure the JIRA® workflow to define how issues will be created, reopened and closed.
-
Configure Sentinel Integration: Start and stop integration, or view the plugin log files.
In the existing version of the plugin, if a user has DAST configured for a group in the WhiteHat Portal that contains DAST, API, or Mobile assets, then if a vulnerability is created for any of those assets, a ticket is created in JIRA. For users migrating to the new version of the plugin, if DAST is configured for that same group, only the DAST assets would sync with JIRA. API and Mobile assets must now be configured separately. |
Once this process is complete, the Issues page displays vulnerability information and key WhiteHat features.