Scenarios for creating a dashboard

A dashboard summarizes the condition of a website by presenting report data from the analysis. You choose the report packs that the dashboard draws its results from. In one situation, each dashboard can represent a different set of issues to be monitored. In another situation, each dashboard can represent a different business unit within the organization. In yet another situation, you can have a dashboard that summarizes similar sets of data; for example, if you have folders broken up by business unit, you can have the dashboard automatically pull report packs from each folder and see all the data in one place.

Here are some scenarios for using dashboards:

  • Each dashboard shows a region of your website and its issues, such as all security and compliance issues on
  • Each dashboard shows a single website's issues, such as a dashboard for that shows all its issues, and a dashboard for that just shows its security and compliance issues.
  • Each dashboard shows certain kinds of issues, such as a compliance dashboard, a security dashboard, or even just security issues and remediation tasks together, with no other reports included.
  • A single dashboard showing all the issues important to an organization

Multiple dashboards for users

The Altoro Mutual company has the following lines of business: information technology, products, and marketing. The users of these business units only want to see information that is relevant to them so they can study their issues and fix them. The company's website is set up traditionally, without a CMS, with each of the business units owning a specific domain, or in the case of IT, all domains. Here is how Altoro Mutual might set up its dashboards:

  1. Create a job that scans the entire website or application.
  2. Create a report pack for each line of business, and base each on the same job.
  3. Create a dashboard for each group or create a single dashboard with a tab for each group. Each tab on a dashboard can be configured to show the data from one or more report packs. If you create a dashboard for each group then you can assign privileges to it to determine who should see its data and who should not. If you create a single dashboard, then everyone with access to the dashboard can see everyone else's issues. The latter situation might not be suitable for an IT group looking at site security issues. However, if users do not have access to the report pack that the dashboard is derived from, then they cannot see detailed report data from that report pack. The only thing these users can see is summary data, such as issues with totals and issue status totals.
  4. If senior management wanted to see all the issues in all areas of the site, then they can have their own dashboard that aggregates the data from all report packs. They can also restrict access to the corporate dashboard to only senior managers.

One dashboard for users

If you want to aggregate all the issues on your site into a single dashboard, which is reviewed by your company executives, you can:

  • Have a single job scan the entire site.
  • Create a single report pack containing all the reports your company is most interested in. In this situation the report pack would contain all security reports.
  • Create a single dashboard that uses the data from the report pack.