> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-1.md).

# 2FA is not enforced in SCM

## Rule Details

|                       |                 |
| --------------------- | --------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_1 |
| Category              | IAM             |
| Severity              | HIGH            |

## Impact

Two-factor authentication (2FA) adds an extra security layer, requiring two authentication factors in order to access the application. Even if user account credentials are compromised, an adversary will not be able to access the application only using the credentials, as they would require the second authentication factor. Currently, 2FA is not enforced for all user accounts, leaving the decision whether to enable 2FA up to the discretion of each individual user.

## Recommended Solution - Buildtime

Enable the option that requires all organization members to set two-factor authentication for their user accounts.

For instructions on how to enable this option, refer to: [Requiring two-factor authentication in your organization](https://docs.github.com/en/github/setting-up-and-managing-organizations-and-teams/requiring-two-factor-authentication-in-your-organization#about-two-factor-authentication-for-organizations).


---

# 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://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/identity-access-management/appsec-cicd-1.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.