> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/data-security-posture-management/how-to-articles/track-your-progress-throughout-your-dspm-journey.md). # Monitoring the DSPM Progress The DSPM (Data Security Posture Management) score serves as a vital tool for monitoring progress within the DSPM framework, particularly in managing the risk associated with sensitive data within the operational ecosystem. This score, quantified on a scale of 1 to 100, offers a concise overview of the percentage of records affected by varying degrees of risk – be it high, medium, or low severity – as identified and flagged by the DSPM module within your operational framework. It aggregates findings from all activated risk rules, thereby enabling customization to align with your specific policy requirements. Typically, customers embark on their DSPM journey with an initial score, endeavoring to enhance it over time by addressing and resolving findings. The DSPM dashboard not only displays your current score but also tracks its evolution over time. Additionally, it highlights the top three risk findings that, once mitigated, would have the greatest positive impact on your score. ![](/files/SuxjAIWNT7CHpaqQmtWz) The dashboard offers filtering options based on projects, labels, and data types. When applying filters, the score dynamically adjusts to reflect only sensitive records corresponding to the selected criteria. This functionality enables customers to evaluate their score tailored to specific use cases, such as: * Displaying the score exclusively for PCI data records. * Highlighting the score for production projects exclusively. #### Score Calculation The Data Security Posture Score reflects the percentage of records deemed at risk within your environment. A posture score of 0/100 indicates that 100% of sensitive records are at high risk, while a score of 100/100 signifies that no records are at any risk. Users can track their current score and observe its fluctuations over the previous 7 days. #### Score Ranges * A score below 60 is classified as high risk and displayed in red. * A score between 60 and 90 is considered medium risk and displayed in orange. * A score above 90 is categorized as low risk and displayed in blue. ### Disclaimer The DSPM Data Security Posture Score intends to provide a summary of the risk level associated with data within the customer's environment. This evaluation relies on the available information within DSPM regarding the customer's configuration and other security related measurements at the time of scoring. However, it does not indicate the likelihood of a customer's system or data experiencing an attack or breach. The DSPM Data Security Posture Score should not be interpreted as a guarantee against security breaches under any circumstances. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.prismacloud.io/content-collections/data-security-posture-management/how-to-articles/track-your-progress-throughout-your-dspm-journey.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.