Dashboard Pack - IT Security Controls Audit Dashboard
This dashboard gives a quick way to identify non-compliant controls for accounts with high privileges.
For each scoped applications you will see:
Server controls (local Administrators)
Application Controls (application level system admins)
DB controls (Database level controls)
How do I import and configure this dashboard?
Ensure you're using Dashboard Server v5.3 or above.
Create a PowerShell profile in Dashboard Server with the following settings:
Note: The name is case-sensitive and must be entered exactly as given here for the tiles to recognise the profile automatically. If you name it differently, you will need to select the profile manually for each tile on the dashboard.
Description (optional) IT Audit profile Script
Copy and paste the contents of the PowerShell script below.
Note: You need to change the values for the parameters to make them work in your environment.PowerShell profile scriptCopy
#Get AD Groups members
$TeamADmin = Get-AdGroupMember -identity "Team1" | Select SamAccountName
$TeamDEV = Get-AdGroupMember -identity "Team2" | Select SamAccountName
$TeamERP = Get-AdGroupMember -identity "TeamERP" | Select SamAccountName
#This is whre you can define the users or AD groups which are authorized to have high privileges rights
$AuthorizedServerAdmins = @(
$AuthorizedDBAdmins = @(
$AuthorizedAppsAdmins = @(
#Option1 - Define list of controls servers
$ScopeServers = @(
#Option2 - Create a SCOM Group to be scope! - if you are using SquaredUp for SCOM
Download and import this dashboard pack.How to import a dashboard pack
Download the dashboard pack zip file for the dashboard pack you wish to import.
There may be additional steps before or after the import to get the dashboard working in your environment.
In Community Edition go to the top right hand menu ☰ > Import Dashboard Packs and drag the zip file into the Manual Import box.
The dashboard pack is imported and if the pack contains top-level dashboards, these will automatically appear in the navigation bar, usually in a folder called 'Community Dashboards' for dashboard packs from the SquaredUp Community.
Carry out any additional steps required to make the dashboard work in your environment. These steps will be described on the download page for each dashboard. For example, you may need to create the correctly named Web API provider, create a PowerShell profile, or edit tile scopes.
Edit the imported dashboard as required.
Edit the PowerShell tiles.
For each tile check the PowerShell script and edit the
$DatabaseNameparameters according to your environment. Check the scripts for other parameters that need to be updated, for example DB connection strings, SQL queries to list Admins from an application, or the fields retrieved by your SQL query.
Edit the tiles by clicking the Edit button.
Open the script panel.
Edit the script according to your environment.
Publish the dashboard.How to publish a dashboard
A newly created dashboard will not be visible to others until you publish it. If you made changes to an existing dashboard, the changes will only be visible to others after you published the dashboard again.
You can identify a dashboard that has not been published yet or has unpublished changes by the unpublished button at the top:
When you click on the unpublished button, you'll have two options:
Publish will make the dashboard or changes visible to others.
Note: A newly created dashboard will appear on the menu where you created it. To move the dashboard to a different place on the navigation bar see How to edit the Navigation Bar.
Discard will delete your draft dashboard if it has never been published or, if you made changes to an already published dashboard, discard the changes.
Publishing dashboards to different audiences