Dashboard

Status Dashboard

DISCLAIMER

• This document contains unedited notes and has not been formally proofread.
• The information provided in this document is intended to provide a basic understanding of certain technologies.
• Please exercise caution when visiting or downloading from websites mentioned in this document and verify the safety of the website and software.
• Some websites and software may be flagged as malware by antivirus programs.
• The document is not intended to be a comprehensive guide and should not be relied upon as the sole source of information.
• The document is not a substitute for professional advice or expert analysis and should not be used as such.
• The document does not constitute an endorsement or recommendation of any particular technology, product, or service.
• The reader assumes all responsibility for their use of the information contained in this document and any consequences that may arise.
• The author disclaim any liability for any damages or losses that may result from the use of this document or the information contained therein.
• The author reserve the right to update or change the information contained in this document at any time without prior notice.
• 
  
• Any attempts to perform penetration testing or ethical hacking on systems or networks should be done with the explicit permission of the system/network owner. Unauthorized access is illegal and can result in serious legal consequences.
• It is important to fully understand the scope of the testing and to only test within that scope. Testing outside the agreed upon scope is considered unauthorized and may result in legal action.
• Any findings or vulnerabilities discovered during testing should be reported to the system/network owner immediately and kept confidential until a fix can be implemented.
• It is recommended to use a separate, dedicated testing environment rather than testing on a live production system to minimize the risk of accidentally causing damage or downtime.
• It is important to take steps to protect your own identity and prevent accidental data leaks or exposure of sensitive information during testing.
• It is also recommended to follow a standard code of ethics for ethical hacking and penetration testing.

***********************************************************************************

Sample Dashboard

Creating a Sample Dashboard with Excel Pivot Tables and Graphs. Rationale for the Parameters Selected in the Dashboard. Different methods are available for creating dashboards, including Power BI and Tableau.

• Region Wise data

• Showcasing the overall - SLA or RAG [Red Amber, Green] status under two categories, to have a better holistic picture.
• Status - Done, next Status - Failed, Pending, canceled and Onhold
• Breaking down the status on which are - Critical, Important and Non-critical, throws light on Severity.

• Resource wise data

• Understanding the cost involved as per resource type.
• Getting info on Mean time to repair MTTR- per resource involved and number of tickets status as per resource group.

• Statutory Wise Data

• The data sets are previewed through the statutory buckets, along with the calendar timeline and asset types involved.

• PIndex Wise Status

• The various categories of Pindex were listed by status, then by quarterly and finally their importance to understand the severity.

Fig 01: Dashboard

Fig 02: Dashboard: Part01

Fig 03: Dashboard: Part02

Fig 04: Dashboard: Part03

Fig 05: Dashboard: Part04

Search keywords: Status Dashboard, GRC, governance, Risk, Compliance, gouti1454, quality management, cybersecurity, information security.