On this page: |
Summary: This page provides instructions for using the Security Dashboard, i.e. how to login, what information is available etc. |
This documentation section provides the following information:
If you need to know more about how to deploy the Security Dashboard, please see: Deploy the CAST Security Dashboard. |
To connect to the Security Dashboard, browse to the URL provided to you by your CAST Administrator. This will usually be in the following format:
http://<server>:[<port>]/CAST-Security |
The login page will then be displayed:
To login to the Security Dashboard, you need to enter a username and password and then click the Log In button.
Depending on the authentication mode configured by the CAST AI Administrator (see Deploy the CAST Security Dashboard for more information) you need to login with a presupplied username and password, or your corporate username and password. If in doubt, contact your CAST AI Administrator.
If for any reason a user cannot access the Security Dashboard (they do not have a login or they have forgotten their password), it is possible to configure a "Can't access" link to be displayed on the dashboard login page. Please see Lost password and request access configuration (from the CAST AIP documentation) for more information. |
This section describes some of the reasons why you may not be able to login to the dashboard:
Note that the message displayed on login can be tailored to your own organization's needs. Please see Modifying login error messages (from the CAST AIP documentation) for more information. |
If you are not authorized to view any data in the Security Dashboard, then upon login a message will be displayed as follows and no further use of the dashboard is allowed:
|
If you attempt to login to the Security Dashboard when no license key has been configured, the following message will be displayed: |
Click the logout button to logout from the dashboard:
By default a session timeout mechanism is in use. When the dashboard detects a session timeout (i.e. there is no GET or POST activity) users will now be notified with an opportunity to continue the session (if within the timeout period) or log back in (if the timeout period has expired) to the system. On timeout, the following dialog box will be displayed - this indicates (in the upper right corner) how many seconds are remaining before a re-login will be required - the default remaining seconds is set to 10. Clicking Continue will return to the session without requiring a login:
Click to enlarge
If the Time left gets to 0, then the Continue button will be disabled and the re-login button will be activated. Clicking Re-login will return the user to the login screen where authentication is required to continue the session:
Click to enlarge
Note that:
|
On login, depending on the number of Applications available, behavior is slightly different:
Number of Applications | Behavior |
---|---|
Single Application | You are taken direct to the Application landing page: |
Multiple Applications | You are offered a choice of which Application to access: When the Application is selected, you will be taken direct to the selected Application's landing page (as shown above). If you are not authorized to access the selected Application, a "You are not authorized to access any applications" message will be displayed. If you would like to choose different Application, you can do so using the dropdown list box located on the menu bar: If you cannot locate the Application you require, you can use the search field to search for the Application - the search is instant - entering a single character will start the search mechanism: |
Whenever relevant, loading icons will display when data could take some time to fetch/process and/or display. |
If, on login, you are presented with the following message on each page in the Security Dashboard, you should contact your CAST Administrator to request that the license is updated:
There are too many authorized users to connect to your Security Dashboard. To avoid this limitation, you can contact your CAST Project Manager to update your licensing terms and conditions. |
You can click the link on the "CAST Project Manager" text o contact the administrator. Doing so will open an email in your default email client requesting that the license is updated. |
This section provides a brief explanation of the interface display options that are available to you.
Note that the tiles displayed out of the box are fully configurable by the CAST AI Administrator. |
The Application landing or "home" page is displayed after a successful login:
It consists of multiple tiles used to display data and information from the most recent snapshot of the selected Application:
This default tile displays "at a glance" information about the current Application status:
All these tiles require that the extension "Quality Standards Mapping" is installed BEFORE a snapshot is generated. |
Various additional tiles are displayed as follows:
When no rules belonging to the selected tag have been triggered, the tile displays "No applicable rules":
Enabling / disabling the Critical Violations filter will effect the violation count displayed in these tiles:
By default, this tile shows two values for the Security Health Measure:
Values are a comparison between the previous and current snapshot, therefore if this is the first snapshot then there will be Added Critical Violations or Violations but no Removed Critical Violations or Violations.
Note that depending on whether Critical Violations or ALL Violations are being displayed (see Data Filtering on Critical Violations), the content will reflect the filter that is currently active, displaying only Critical Violations or ALL Violations accordingly. |
Clicking the tile will take you directly to the Health Measure in the Risk Investigation view (see Using the CAST Security Dashboard for more information), however, the Risk Investigation view will only show added and removed violation information. Any Health Measure, Technical Criterion or Rule where the number of Added and/or Removed violations is 0, will not be visible. A message will reflect this:
This default tile displays "at a glance" information about the Violation status for the current Application:
Clicking this tile will take you directly to the Application investigation view (this can also be accessed by clicking the button available in the sidebar).
A "Top Riskiest Transactions tile" is provided "out-of-the-box" for the Security Health Measure:
This tile provides a clickable "cloud" of transaction names - the larger and bolder the font used to display the transaction name, the higher the TRI value (TRI or Transaction Risk Index is an indicator of the risk for transaction) has within the Security Health Measure.
Clicking a transaction name in the tile will take you directly to the parent Health Measure in the Transaction Investigation view (this can also be accessed by clicking the button available in the sidebar):
Click to enlarge
A "Top Riskiest Components tile" is provided "out-of-the-box" for the Security Health Measure:
This tile provides a clickable "cloud" of object names - the larger and bolder the font used to display the name, the higher the Risk (previously known as PRI: Propagated Risk Index) value the object has within the Security Health Measure. See this table for more information about how Risk is calculated.
Clicking an object name in the tile will take you directly to the object in the Application Investigation view - for example clicking the MFJDEMUT object will show this (click to enlarge):
One "Top Modules with Violations" tile is provided "out-of-the-box" for the Security Health Measure:
This tile provides a listing of the modules sorted by the number of violations / critical violations present in each module. Tile can be resized to display more or less modules. Clicking a module in the tile will take you directly to the module in the Application Investigation view. In the Application Investigation view, violated Rules are listed by their number of violations, with critical rules first (by default: ordered by number of violations):
Note that depending on whether Critical Violations or ALL Violations are being displayed (see Data Filtering on Critical Violations), the content will reflect the filter that is currently active, displaying only Critical Violations or ALL Violations accordingly. |
Two tiles listing the Strength and Weakness of the Security Health Measure, listed by Technical Criteria:
Note that depending on whether Critical Violations or ALL Violations are being displayed (see Data Filtering on Critical Violations), the content will reflect the filter that is currently active, displaying only Critical Violations or ALL Violations accordingly. |
These tiles provide
Clicking a Technical Criterion in the tile will take you directly to the Technical Criterion in the Risk Investigation view:
A "Top Rules with increasing violations" tile is provided "out-of-the-box" for the Secure Coding - Input Validation technical criterion:
These tiles displays Top Rules with increasing violations: the value represents the difference (increase) in the number of violations for the Rule between the most recent and the previous snapshot. The higher the value, the larger the difference, i.e. those Rules listed at the top of the list have MORE violations since the previous snapshot.
Violation count difference is displayed on the right of a rule and a red dot is added when the rule is critical. Rules are clickable and will take you direct to the Rule in the Risk Investigation view.
Note that the default behaviour in the dashboard is to display ONLY Critical Violations (see Data filtering on Critical Violations) - therefore the display in this tile will reflect this and only Critical Violations (with a red dot) will be displayed. If the default filter is disabled to show ALL violations, then the tile will display Critical and non-Critical Violations. |
A default Action Plan tile is displayed showing, initially, the total number of objects that have been added to the Action Plan list since the last snapshot was generated. Clicking the tile will take you directly to the Action Plan).
This tile can be manually re-sized (drag and drop the corners or sides of the tile) to include more information about Pending and Solved items (see the Action Plan for more information about the Pending and Solved statistics):
A default Exclusions tile is displayed showing:
Clicking the tile will take you to the relevant Exclusion page, see Security Dashboard - Exclusions for more information.
Default tile: | Small size: |
A "Continuous Improvement" tile is available out of the box:
As explained previously the landing page or home page contains a set number of "default" tiles that are delivered "out of the box". Your dashboard Administrator may chose to configure additional tiles or custom locations for the default set of tiles but you have a certain amount of freedom to set up the home page as you require:
Changes you make to the location or size of tiles is saved via a cookie, therefore the positions and sizes of tiles will be retained over successive sessions using the same browser. Using a different browser on the same workstation will not retain the changes to the tiles.
If you would like to reset the position and size of the tiles as they are provided to you "out of the box", you can use the Reset homepage option located in the top right hand corner:
If you would like to monitor a specific Rule (perhaps a critical Rule with multiple violations) in your Application via a tile in the landing/home page you can do so by adding a "bookmark" or "favorite" tile which links to the item in question. To do so:
Tips:
|
Each tile displayed in the landing or home page will be configured with a predefined colour. However, you can change this from your browser:
|
By default, the Security Dashboard is delivered with language display set to English: all messages and text displayed in the dashboard is only displayed in English. However, it is possible to choose a specific language locale and provided that a translation of the default English text and messages has been configured (see Dashboard localization in the CAST AIP documentation), the dashboard will then display text and messages in the chosen language. To do so, click the user menu drop down and select the the Change Language option:
A popup window will then enable you to select the required language - choose the language and click Change:
The dashboard will then reset and text items will be displayed in the chosen language.
Note that:
|
A description of each numbered item is provided below:
Item | Name | Description | |
---|---|---|---|
1 | Application selector | This option enables you to select the Application you wish to view. A drop down list box will be displayed enabling you to pick the Application you require. Note that only the Applications you are authorized to view will be available for selection. | |
2 | Snapshot description | Displays information about the current snapshot data you are viewing: Name, Version, Date. | |
3 | Snapshot selector | This option enables you to select a specific snapshot to investigate - if multiple snapshots are available for the current Application. This allows you to "go back in time" and investigate data from a previous snapshot. Note that not all data is available for previous snapshots. See snapshots for more information. | |
4 | Share data | Clicking this icon will open a new email in your default email client, together with a link to the current location in the dashboard. You can therefore use option to share a link with colleagues. Example email shown below:
| |
5 | Data filtering | This icon activates/deactivates data filtering on Critical Violations. By default, only Critical Violations are displayed. See Data filtering on Critical Violations for more information. | |
6 | Search (basic) | Activates a basic search field enabling you to search for names of items in the Assessment Model:
A search made in Home page, Risk Investigation view, Transaction investigation view and Action/Exclusion lists will give results for the following items:
A search made in Application investigation view will give results for the following items:
| |
7 | Current user | Indicates the name of the current user that is logged in to the Security Dashboard. A drop down list box is also available: This contains the following options:
|
Side menu | Item | Name | Description |
---|---|---|---|
1 | Home | This button will take you back to the initial "home" or landing page from wherever you are located in the Security Dashboard. | |
2 | Risk Investigation view | This option focuses on application risk level from the Assessment Model perspective - moving through Business Criteria, Technical Criteria, Rules/Measures/Distributions right down to the objects in violation. | |
3 | Application Investigation view | This option focuses on the application's technical components (i.e. its objects) and provides violation details on those objects and their related dependencies. | |
4 | Transaction Investigation view | This option focuses on the application's transactions and provides violation details on the riskiest transactions and their related dependencies. | |
5 | Advanced search | This option allows you to search for an object name based on a list of violations. Filters can be enabled to limit the search scope. | |
6 | Education / Continuous Improvement | This option provides access to the Education / Continuous Improvement features. By default, the focus will be on the Education feature. | |
7 | Actions / Exclusions | This option provides access to the Actions / Exclusions features. By default, the focus will be on the Action Plan feature. | |
8 | Report Generation | Provides access to the Report Generation feature. | |
9 | Contextual help | This option provides basic help for various items in the Security Dashboard. To use it:
|
Note that the Security Dashboard features a server cache to improve the speed of data display. This does mean, however, that very recent changes in data (i.e. a new snapshot generation) may not instantly appear in the dashboard. If this is the case, the server cache needs to be manually reloaded. See Reload the cache (from the CAST AIP documentation). |
The information displayed in the Security Dashboard is derived from snapshots generated by the CAST AI Administrator and provides a detailed "engineering" level view of your set of Applications - this includes specific information about Rules and Violations.
All data that is displayed is taken from the most recent snapshot that has been generated for the selected Application. However, it is possible to view data from a previous snapshot if required by using the snapshot selector in the top menu:
Clicking this option will display a drop down menu where you can select the snapshot you require:
To view a previous snapshot, select it on the timeline and then click the Select Snapshot option:
The display will then update to show the data from the selected snapshot.
Note that when viewing data from a previous snapshot, some information/tiles are not available:
|
To return to the current snapshot data use the snapshot selector button on the top menu bar to select the most recent snapshot:
By default, the Security Dashboard only shows information about Critical Violations, rather than showing data for ALL violations - this allows you to instantly see the most important flaws in the analyzed application.This data filter is controlled by the following icon in the Top Menu bar:
When in the default position showing only information about Critical Violations, the icon is colored red as shown above. When in this position, the dashboard only shows information about Critical Violations and other non-Critical Violations are ignored. For example, the Risk Model tile will display data only about Critical Violations (as specified in the black circle):
Note that:
|
If you would prefer to view all data about ALL Violations (not just Critical Violations) in your application, you can disable the filter by clicking the filter icon on the top menu:
Once the filter is disabled, ALL data is now displayed. For example the Risk Model tile now displays data about ALL violations:
The data available is displayed using various different "views":
Accessible from the sidebar menu or by clicking the Risk Model tile, this view enables investigation of the application risk from the Assessment Model perspective - moving through Health Measures/Business Criteria, Technical Criteria, Rules/Measures/Distributions right down to the objects in violation.
By default, only Business Criteria that are categorised as Health Measures will be displayed in the dashboard. All other Business Criteria that are NOT Health Measures will not be displayed. You can override this behaviour, to display ALL top-level Business Criteria if required - see Dashboard wide configuration options in json from the CAST AIP documentation.
Data is presented in a series of tables on the left and right hand side of the page enabling you to drill down from a Health Measure to an individual object that is in violation. Take for example the top level list of Health Measures:
Selecting a Health Measure in this table will display all of the contributing Technical Criteria in the right hand section:
When a Health Measure is selected, the first row in the Technical Criteria list will be titled "All Rules...". Selecting this item will display a list of all the Rules that contribute to the selected Health Measure: |
Selecting a Technical Criteria will move the Technical Criteria to the left hand side of the page and display all of the contributing Rules in the right hand section:
Selecting a contributing Rule will move the item to the left hand side of the page and display details about it (including the list of objects in violation, computing details, and rule/distribution/measure documentation) in the right hand section:
Note that when there are many violations to display, a "Show More" button will be available: By default, only 10 violations are displayed to improve performance. You can choose to display more using the various options (+10, +100 etc.). By default an upper maximum of 5000 violations is set when the "All" option is clicked. You can change the upper maximum if required (see the violationsCount option in Dashboard wide configuration options in json from the CAST AIP documentation). |
Finally, depending on the item (Rule, Distribution, Measure), you can do as follows:
For a Rule the following sections are available:
Expand the list of Violations
...to view the objects violating the selected Rule:
The following icons will be available:
Educate | Click this icon to add the associated Rule to the Security Dashboard - Education list. |
Download | Click this icon to export the list of violations to Excel. |
Note that Source Code is not available when viewing data from a previous snapshot. |
Select an object in the list of violations to view its source code. In order to focus investigation, source code displayed presents either:
Whenever a piece of code is made available, the View File button (seen in the example below) provides the ability to open the entire source code file to get the entire context. The file is opened in a separate browser window. The entire source code is presented plus some context (application name, snapshot reference, file name).
The Rule name is also highlighted using colour (yellow for a standard Rule (as shown below), and red for critical):
Please note that in the current release of CAST AIP, the display of source code is limited in functionality:
|
When a Rule involves "cyclical calls" such as the rule "Avoid cyclical calls and inheritances between packages", then the source code display is altered slightly as follows. A cyclical call means two packages refer to each other through a call and therefore, the result of this could be a circular dependency. So in this case, the dashboard does not show the detailed source code but the list of packages involved so that we can show where these cyclical calls are located.
If a "copy/pasted" Rule has been selected (for example Avoid Too Many Copy/Pasted Artifacts), a list of objects that have a high level of similarity with the selected objects will be listed:
After clicking on the object in the Violation details table, a separate page will be opened to show the comparable code fragments (see image below - click to enlarge):
When results include violation bookmarks in the source code, the dashboard can access more details about the actual defects in the object for the current Rule. The violation bookmarks are displayed per defects found; the display follows the same pattern as the object source code viewer: each code fragment is associated to its related file and the violation bookmark is highlighted using colour (yellow for a standard Rule, red for critical (as shown below). Multiple bookmarks may be associated to a single defect (as shown below):
A More defects button will appear when there are more than five defects in the object for the current Rule:
If a defect contains multiple bookmarks, then the Primary/Secondary bookmark will appear to show the main bookmark and additional bookmarks as shown below. The display follows the same pattern as the object source code viewer, except that the secondary bookmark will be highlighted as blue:
A More bookmarks button will appear when there are more than five bookmarks in one defect for the current Rule. The color depends on whether the Rule is critical (red) or not (yellow). If you click "View File" button, the lines numbers are highlighted:
Bookmarks for defects in source code violating OWASP Rules (such as Avoid SQL injection vulnerabilities ( CWE-89 ) ) are displayed slightly differently to help you follow the violation trail within the Application:
You can use the "eye" icon to the right of the list to view the source code file in which the bookmark is located:
The Violation details section underneath the Source Code display shows the Violation Name along with the values of the Violation Details (i.e the "Associated Values"):
If the Rule does not have any violation details, the message "No violation details for this Rule" will be displayed instead. |
You can use the Why is that an issue? option underneath the Source Code display to view the Rationale section of the Rule that has been violated. Clicking the Learn More button will take you directly to a full description of the violated Rule:
This section displays:
Column | Explanation |
---|---|
Module | Shows the name of each module that has objects as defined during the snapshot configuration and generation. |
Total Check | The total number of objects in the module that were checked against the current Rule. |
Viol. | The number of objects in the module violating the current Rule. |
Compliance | The compliance rate for the module - i.e. the percentage of objects in the module that are compliant with the Rule. |
Note that the row containing the module name "Total" contains cumulative data for all modules displayed in the section. |
Clicking the following icon will take you directly to the object in the Application Investigation view:
For a Distribution, you can view how objects in the current Application are distributed: objects are placed into categories depending on the criteria of the Distribution itself. Sections indicate which category the objects fall into: Low/Small (Green), Average, High/Large and Very High/Very Large (Red). A Status column displays the status of the object between the current and previous snapshot (unchanged, added, deleted etc.). So to take the example of the Size Distribution distribution:
Quality Measures are listed in the Security Dashboard, however, since Measures are never "violated" in the same way a Rule is violated, little information can be displayed other than the documentation:
All tables that display data in the Risk Investigation mode contain various columns. The table below lists all possible column names and provides an explanation for each:
Column | Explanation |
---|---|
![]() | Displays the number of Violations or Critical Violations added to the current snapshot for the currently selected item since the last snapshot. |
![]() | Displays the number of Violations or Critical Violations removed from the current snapshot for the currently selected item since the last snapshot. |
#Critical / #Violations | Displays the number of Violations or Critical Violations for the currently selected item. This column is also used as the default sorting criteria when items are first displayed. |
Previous | Displays a % variation of the number of Violations or Critical Violations in the current snapshot for the currently selected item compared with those in the previous snapshot. |
Health Measure | Name of the Health Measure |
Column | Explanation |
---|---|
![]() | Displays the number of Violations or Critical Violations added to the current snapshot for the currently selected item since the last snapshot. |
![]() | Displays the number of Violations or Critical Violations removed from the current snapshot for the currently selected item since the last snapshot. |
#Critical / #Violations | Displays the number of Violations or Critical Violations for the currently selected item. This column is also used as the default sorting criteria when items are first displayed. |
Previous | Displays a % variation of the number of Violations or Critical Violations in the current snapshot for the currently selected item compared with those in the previous snapshot. |
Technical Criterion | Name of the Technical Criterion. |
Weight | Displays the weight of the Technical Criterion in its parent Health Measure. The higher the value, the more weight the item carries. |
Column | Explanation |
---|---|
![]() | Displays the number of Violations or Critical Violations added to the current snapshot for the currently selected item since the last snapshot. |
![]() | Displays the number of Violations or Critical Violations removed from the current snapshot for the currently selected item since the last snapshot. |
#Critical / #Violations | Displays the number of Violations or Critical Violations for the currently selected item. This column is also used as the default sorting criteria when items are first displayed. |
Evolution | Displays a % variation of the number of Violations or Critical Violations in the current snapshot for the currently selected item compared with those in the previous snapshot. |
Rules... | Name of the Rule/Distribution/Measure. |
Weight | Displays the weight of the Rule/Distribution/Measure in its parent Technical Criterion. The higher the value, the more weight the item carries. |
Critical Rule | A red dot in this column indicates that the Rule has been set as critical in the Assessment Model. |
Column | Explanation | ||||
---|---|---|---|---|---|
Option to add/remove the violation from the Action Plan or the Scheduled Exclusion List (see Security Dashboard - Action Plan for more information). Note that to interact with the Action Plan/Scheduled List, your user login must have the role QUALITY_MANAGER/EXCLUSION_MANAGER roles. These can be assigned at user level (when using Default Authentication mode) or via user or group (when using Standard LDAP authentication). Please see Configuring user authentication for more information. | |||||
Action / Exclusions | Indicates whether the violation has been added to the Action Plan or the Scheduled Exclusion List (see Security Dashboard - Action Plan for more information):
| ||||
Object Name Location | Displays the object name, and in the case of file based objects (as oppose to Database objects), the location on disk of the object. | ||||
Risk | This value was previously known as Propagated Risk Index (PRI): it identifies the violations that can impact the largest number of components, involving objects with the largest number of violations pertaining to the Health Measure involved. The formula used to calculate this value is as follows:
Where RPF and VI equal: RPF Risk Propagation Factor (RPF): identifies violations that can impact the largest number of components in the Application. The impact area is computed as follows:
VI Violation Index (VI): identifies objects with the largest number of violations, taking into account the weight of the Rules and of the Technical Criteria, for the Health Measure involved. The formula used to calculate this value is as follows For each object, identify Rules it violates that contribute to a given Health Measure through Technical Criteria. Multiply aggregate weight of the Rule within the Technical Criterion by the aggregate weight of the Technical Criterion within the Health Factor. In other words:
| ||||
Status | Displays the status of the object in comparison to the previous snapshot - e.g.:
You can also filter on a status by selecting the column header and choosing the status you want to view: | ||||
Clicking this icon will take you direct to the object in the Application Investigation view. |
Column | Explanation |
---|---|
Object Name Location | Displays the object name. |
Status | Displays the status of the object in comparison to the previous snapshot - e.g.:
You can also filter on a status by selecting the column header and choosing the status you want to view: |
Measures only display the documentation.
Each table displays Business Criteria, Technical Criteria and Rules/Distributions/Measures based on the following specific criteria:
For Rules only:
By default when using the Risk Investigation view, the entire Application content is displayed. However, you may be interested in investigating a subset of the Application (a specific module or a specific technology). Two filters are available for that purpose in the breadcrumb area,to the top right.
Some filtering may not be relevant as you drill down. If you are investigating a SQL specific rule and try to filter on others technologies (for example), we would get no data, hence, to make things clearer, the other technology filters are disabled (lighter grey colour) in this context. This can apply at technical criteria or Rule level and in some rare cases, even from the Health Measure level:
|
Note that the Application Investigation view is not available when viewing data from a previous snapshot. |
Accessible from the sidebar menu or by clicking the Application Components tile, this view enables investigation of the objects in the Application. Data is presented in a series of tables on the left and right hand side of the page enabling you to drill down from an Application right down to an individual object within that Application, and view the Rules that those objects have violated.
The default Health Measure used for this view is Security:
The Application Browser provides a hierarchical tree view of the Application, its modules and the individual projects and objects that make up the Application:
Selecting an item in the tree will do two things:
When applications are large and flat (flat project structure), the number of items can be large, leading to slow loading and page rendering. A pagination mechanism has been designed in order to improving the usability: only a subset of items are loaded (~100 by default) and, upon scroll in the browser, more content will load in a lazy fashion with the message "Loading Next Items":
Selecting an item (Application, Module, Project, Object) in the left hand section will update the right hand section. This section lists Rules that the selected item is violating and the object's Technical Properties (see below). Rules are listed by the number of times they have been violated by the selected item (and all its constituent items in the case of an Application, Module or Project) and whether the Rule is critical (flagged with a red dot):
Click to enlarge
Note that an icon indicates the list you are working in: |
Column | Explanation | |
---|---|---|
Name | Name of the Rule that the selected item is violating. | |
#Violations / #Critical Violations | The number of Critical Violations or Violations that the selected Rule has (the display depends on whether only Critical Violations or ALL Violations are being displayed (see Data Filtering on Critical Violations)). | |
Weight | Displays the compounded weight of the Rule in the parent Technical Criterion. The higher the value, the more weight the Rule carries. Clicking the Weight column header will sort the Rules as follows:
Compounded weight is calculated as follows:
| |
Critical Rule | A red dot in this column indicates that the Rule has been set as critical in the Assessment Model. |
Selecting an item (Application, Module, Project, Object) in the left hand section will update the right hand section. This section lists Rules that the selected item is violating (see above) and the object's Technical Context. This section displays the properties of the selected objects. It has two views:
Note that:
|
Clicking a Rule in the right hand section will move the right hand panel over to the left hand side, and display a new panel containing:
|
The following icons will be available:
Educate | Click this icon to add the associated Rule to the Security Dashboard - Education list. |
Download | Click this icon to export the list of violations to Excel. |
Selecting an object in the Violations and Rule Documentation section will move the right hand panel over to the left hand side, and display a new panel containing the source code of the selected object:
Accessible from the sidebar menu or by clicking an object in the Top Riskiest Transactions tile, this view enables investigation of the transactions in the Application. Data is presented in a series of tables on the left and right hand side of the page enabling you to drill down from a Transaction with a high level of risk (i.e. Violations) right down to the Violations themselves.
The view functions in a very similar way to the Risk Investigation view. The default Health Measure used for this view is Security.
The view lists 50 Transactions per "page" sorted by the risk level (i.e. the Transaction Risk Index (TRI) value: TRI is an indicator of the riskiest transactions of the application. The TRI number reflects the cumulative risk of the transaction based on the risk in the individual objects contributing to the transaction. The TRI is calculated as a function of the rules violated, their weight/criticality, and the frequency of the violation across all objects in the path of the transaction. TRI is a powerful metric to identify, prioritize and ultimately remediate riskiest transactions and their objects.)
Selecting a transaction will display information in the right hand panel about the status of each Health Measure:
Column | Explanation |
---|---|
![]() | Displays the number of Violations or Critical Violations added to the current snapshot for the currently selected item since the last snapshot. |
![]() | Displays the number of Violations or Critical Violations removed from the current snapshot for the currently selected item since the last snapshot. |
#Critical / #Violations | Displays the number of Violations or Critical Violations for the currently selected item. This column is also used as the default sorting criteria when items are first displayed. |
Health Measure | Name of the Health Measure/Business Criterion |
Selecting a Business Criteria in this table will display all of the contributing Technical Criteria in the right hand section:
Column | Explanation |
---|---|
![]() | Displays the number of Violations or Critical Violations added to the current snapshot for the currently selected item since the last snapshot. |
![]() | Displays the number of Violations or Critical Violations removed from the current snapshot for the currently selected item since the last snapshot. |
#Critical / #Violations | Displays the number of Violations or Critical Violations for the currently selected item. This column is also used as the default sorting criteria when items are first displayed. |
Technical Criterion | Name of the Technical Criterion. |
Weight | Displays the weight of the Technical Criterion in its parent Health Measure/Business Criterion. The higher the value, the more weight the item carries. |
Selecting a Technical Criteria will move the Technical Criteria to the left hand side of the page and display all of the contributing Rules, Distributions and Measures in the right hand section:
Column | Explanation |
---|---|
![]() | Displays the number of Violations or Critical Violations added to the current snapshot for the currently selected item since the last snapshot. |
![]() | Displays the number of Violations or Critical Violations removed from the current snapshot for the currently selected item since the last snapshot. |
#Critical / #Violations | Displays the number of Violations or Critical Violations for the currently selected item. This column is also used as the default sorting criteria when items are first displayed. |
Names | Name of the Rule/Distribution/Measure. |
Weight | Displays the weight of the Rule/Distribution/Measure in its parent Technical Criterion. The higher the value, the more weight the item carries. |
Critical Rule | A red dot in this column indicates that the Rule has been set as critical in the Assessment Model. |
Selecting a contributing Rule, Distribution or Measure will move the item to the left hand side of the page and display details about it (including the list of objects in violation and rule/distribution/measure documentation) in the right hand section:
Note that when there are many violations to display, a "Show More" button will be available: By default, only 10 violations are displayed to improve performance. You can choose to display more using the various options (+10, +100 etc.). By default an upper maximum of 5000 violations is set when the "All" option is clicked. You can change the upper maximum if required (see the violationsCount option in Dashboard wide configuration options in json - from the CAST AIP documentation). |
The following icons will be available:
Educate | Click this icon to add the associated Rule to the Security Dashboard - Education list. |
Download | Click this icon to export the list of violations to Excel. |
The Security Dashboard features the ability:
See:
The Report Generation feature allows you to generate reports on the fly direct from the CAST Security Dashboard interface. Various reports can be generated, however, some require some configuration before they will work. See Security Dashboard - Report Generation for more information:
The Advanced Search feature can be accessed using the icon in the left hand menu:
"Out of the box", the Advanced Search feature is not enabled and the following message will be displayed:
This indicates that a "violations index" (on which the feature relies) has not yet been generated. To generate the index the following methods are available:
Using the "Diagnostic" GUI |
Use the following URL to access the Diagnostic page:
This provides an indication of the violations index status based on the "domain":
In the following example the index has never been generated since the status is set to "toCreate": Click to enlarge To generate the index, click the Create/Update Index button. During generation the status "Indexing" will be displayed and on completion, the status will change to "upToDate": Click to enlarge | ||||
---|---|---|---|---|---|
Using the RestAPI |
Use the RestAPI client:
Using the following URI with a PUT will generate the index (where <domain> is more than likely set to AED, unless you have custom domains):
Then use the same URI with a GET will show the index status: | ||||
Generating the index when the web application starts | This method will force the violations index to be generated if its status is toUpdate (i.e. the index exists but is out-of-date because a new snapshot has been computed since the index creation) every time the web application is started, i.e.:
Edit the following file with a text editor:
Set the following configuration to true:
Save the file. Next time the web application is started the index will be generated. | ||||
Using a custom batch file |
This method is to be used when you have a configuration in the domains.properties file - i.e. multiple "domains". The custom batch will generate the violations index for all the domains configured in the domains.properties file. Create the following batch files in the %CATALINA_HOME%\webapps\<dashboard>\WEB-INF folder an then run the launch.bat file to start the index generation:
In the following file (titi.bat), you need to modify the line starting curl to match your environment:
|
Note that following the generation of a new snapshot, the violations index status will change to toUpdate, therefore CAST recommends regenerating the index to take into account the data available in the new snapshot. |
When the feature is accessed and the violations index has been generated, the following will be displayed:
Left hand panel | The left hand panel provides a set of filters that can be used to narrow down the search cope. Filters are explained in XXXX. | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Right hand panel | The right hand panel list the results of the search. Key points:
|
The filters available in the left hand panel enable the search scope to be limited. The following filters can be enabled by expanding the section and selecting with a tick:
Criteria or Rules | Restrict the scope via a Health Measure, Technical Criterion or Rule (or a combination). Displayed results are union of selected Criteria results, with duplicate violations omitted. Sorting is disabled on this section. |
---|---|
Weight | Restrict the scope via the weight of the rule in its parent Technical Criterion. |
Criticality | Restrict the scope via the criticality of the rule (Critical or Non Critical). |
Violation Status | Restrict the scope to the violation status in the current snapshot: Added, Updated, Unchanged. Displayed results are an OR of selected violation status results and AND of other filters selected values (eg : Criteria or rules, Technologies ,Transactions , Critical ,Module) with duplicate violations omitted. Violation status remains selected even after navigating to other views and coming back to Advanced search. |
Transactions | Restrict the scope to objects that are classed as transactions. |
Technologies | Restrict the scope to the technologies that are present in the current snapshot. Displayed results are an OR of selected technologies results and AND of other filters selected values (eg : Criteria or rules, Modules ,Transactions , Critical ,Violation status) with duplicate violations omitted. |
Modules | Restrict the scope to a module in the current snapshot. Displayed results are an OR of selected module results and AND of other filters selected values (eg : Criteria or rules, Technologies ,Transactions , Critical ,Violation status) with duplicate violations omitted. Module remains selected even after navigating to other views and coming back to Advanced search. |
Note that an indicator will show how many filters have been selected: |
You can export data to an Excel file format if required. To export to Microsoft Excel file format, use the following icon which is available at the following levels:
When you click this icon, depending on your browser you will be prompted whether you would like to Save or Open the Excel file. The Excel file will contain the data you requested in column format:
Notes about the Excel file data:
|
When you export to Excel from the Violation level, a column containing a Rule's Associated Value may also be available in the resulting Excel file - in the example below, "JSP Page name" is the Associated Value for the Rule "Action Artifacts should not directly call a JSP page":
The Associated Value refers to a specific output for the Rule in question. For the Rule shown above "Action Artifacts should not directly call a JSP page", the Associated Value is defined as the JSP Page name - in other words, for this Rule, the JSP file listed in the column highlighted above violates the Rule in question. You can view the Associated Value configuration in the CAST Management Studio by opening the Assessment Model and locating the Rule:
The Security Dashboard features the ability:
See:
The Report Generation feature allows you to generate reports on the fly direct from the CAST Security Dashboard interface. Various reports can be generated, however, some require some configuration before they will work. See Security Dashboard - Report Generation for more information: