> 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-configuring-user-login-protection-methods-on-critical-access-system.md).
# How To Resolve Sprinto Check For Configuring User Login Protection Methods On Critical Access System
### About
Sprinto check: Access to critical system should be protected with a secure login mechanism
The use of a secure login mechanism for accessing critical systems helps enhance the system’s security. Login mechanisms like Single Sign-On (SSO), Multi-Factor Authentication (MFA), Complex Password, or Virtual Private Network (VPN) can be defined against the critical system.
### Purpose
The purpose of this check is to ensure that a secure login mechanism is configured and defined on Sprinto against the critical system.
### Procedure
Follow the below procedure to define the login protection method:
1. From the Sprinto admin portal, navigate to Data Library > Access, then select the Overview tab.
2. Select any integrated critical system from the list you wish to configure.
3. Select the Summary tab, and click Configure now under the Accounts.
4. Click Configure/ Edit next to the Login Protection Method section.
5. Select the login protection methods configured to access the selected critical system.
6. Once selected, click Save to apply the changes.
### What’s next
Sprinto will now periodically remind you to upload evidence showcasing the implemented login protection methods for the critical system.
### Support
Please get in touch with our [support team](mailto:www.support@sprinto.com) if you need any assistance with the above Sprinto check.
---
# 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-configuring-user-login-protection-methods-on-critical-access-system.md?ask=&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.
