> 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-70.md). # Access key with a weak SSH signature was detected in SCM ## Rule Details | | | | --------------------- | ---------------- | | Cortex AppSec Rule ID | APPSEC\_CICD\_70 | | Category | IAM | | Severity | LOW | ## Impact Repository access keys created with weak signature algorithms can allow attackers to perform a Man In The Middle attack and compromise the integrity and confidentiality of the communications with the SCM. An access key created with the deprecated ssh-dss algorithm is in use in the Bitbucket workspace. The algorithm was deprecated in OpenSSH 7.0: ## Recommended Solution - Buildtime Revoke all **ssh-dss keys** in use. Instead, use any of the following supported **OpenSSH** key types: * ecdsa * ecdsa-sk * ed25519 * ed25519-sk * rsa To replace an access key: 1. Create a new private key on the server intended to use it, using one of the recommended algorithms. 2. Create a new access key using the matching public key in the same repository that the current key was created on. 3. Direct the server to use the new access key. 4. Delete the older access key from the Bitbucket repository. ### Create and delete access keys * Create and delete access keys through the console: Browse to the **Deploy Keys** tab under the repository **Settings**. * Create and delete access keys through the API: Refer to the Bitbucket API documentation:. --- # 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-70.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.