> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/monitors/workflow-check-resolution/how-to-resolve-sprinto-check-for-critical-systems-access-review.md).

# How to resolve Sprinto check for critical systems access review

### About

Check: Periodic Review of Access to Critical Systems Completion

The above Sprinto check serves as a reminder to perform the users access review for the critical system. The review is a periodic process and need to be repeated every twelve months. The review by default needs to be performed by the assigned InfoSec officer. However if you have assigned critical system owner, either the owner or InfoSec officer can perform the review.

### Purpose

The need for performing access review periodically is to ensure that the organization's critical resources are accessed only by authorized staff members. Access validity for a critical system can be configured through various means, including:

Note: By default, the check’s frequency is set as 12 months. You can update the frequency per your need, if required.

* Accessible by all staff members
* Role-based access
* Ticket-based access

### How to Resolve

To resolve this check, review the staff members access to the critical systems. Ensure only the valid staff members accesses the critical systems in accordance with the configured access control settings for each system.

For detailed instructions, please refer to perform[ critical system access review](https://sprinto.freshdesk.com/support/solutions/articles/72000606020-how-do-you-perform-users-access-review-for-critical-systems) for detailed instructions.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sprinto.com/monitors/workflow-check-resolution/how-to-resolve-sprinto-check-for-critical-systems-access-review.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.