change a.c node names

[YiscahLevySilas1]

PR Type:

Refactoring

---

PR Description:

This PR includes changes to the node names in various files. The changes are mainly semantic, aiming to make the node names more descriptive and accurate. The files affected include various control and attack-track files.

---

PR Main Files Walkthrough:

attack-tracks/service-destruction.json: The node name "Workload Exposure" has been changed to "Exposed Workload", and "Service Destruction" has been renamed to "Denial of service".
attack-tracks/workload-external-track.json: Several node names have been updated for clarity, including "Workload Exposure" to "Exposed Workload", "Data Access" to "Data Exposure", "Secret Access" to "Secret Exposure", "Credential access" to "Credential Exposure", "Potential Node exposure" to "Vulnerable node", and "Network" to "Network Exposure".
controls/C-0009-resourcelimits.json: The category "Service Destruction" has been renamed to "Denial of service".
controls/C-0041-hostnetworkaccess.json: The category "Network" has been renamed to "Network Exposure".
controls/C-0044-containerhostport.json: The category "Workload Exposure" has been renamed to "Exposed Workload".
controls/C-0045-writablehostpathmount.json: The category "Potential Node exposure" has been renamed to "Vulnerable node".
controls/C-0046-insecurecapabilities.json: The category "Potential Node exposure" has been renamed to "Vulnerable node".
controls/C-0048-hostpathmount.json: The category "Potential Node exposure" has been renamed to "Vulnerable node".
controls/C-0255-workloadwithsecretaccess.json: The category "Secret Access" has been renamed to "Secret Exposure".
controls/C-0256-exposuretointernet.json: The category "Workload Exposure" has been renamed to "Exposed Workload".

---

User Description:

Overview

[codiumai-pr-agent-free]

PR Analysis

• 🎯 Main theme: Refactoring node names for clarity and accuracy
• 📝 PR summary: This PR focuses on renaming various node names across multiple files to make them more descriptive and accurate. The changes are primarily semantic and affect various control and attack-track files.
• 📌 Type of PR: Refactoring
• 🧪 Relevant tests added: No
• 🔒 Security concerns: No security concerns found

PR Feedback

• 💡 General suggestions: The changes made in this PR are primarily semantic and do not affect the functionality of the code. However, it is important to ensure that these changes are reflected in any documentation or comments that reference these node names. Additionally, any tests that rely on these node names should be updated to reflect the changes.

• 🤖 Code feedback:

  • relevant file: attack-tracks/service-destruction.json
    suggestion: Ensure that the renaming of the nodes does not affect any dependencies that might be present in other parts of the codebase. [medium]
    relevant line: "name": "Exposed Workload",

  • relevant file: controls/C-0041-hostnetworkaccess.json
    suggestion: Make sure that the new node names are consistent across all files and that they accurately represent the functionality of the node. [medium]
    relevant line: "Network Exposure"

  • relevant file: controls/C-0046-insecurecapabilities.json
    suggestion: Check if there are any hardcoded values or tests that rely on the old node names and update them if necessary. [medium]
    relevant line: "Vulnerable node"

  • relevant file: controls/C-0259-workloadwithcredentialaccess.json
    suggestion: Ensure that the renaming of the nodes does not affect any dependencies that might be present in other parts of the codebase. [medium]
    relevant line: "Credential Exposure"

How to use

To invoke the PR-Agent, add a comment using one of the following commands:
/review [-i]: Request a review of your Pull Request. For an incremental review, which only considers changes since the last review, include the '-i' option.
/describe: Modify the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest improvements to the code in the PR. Extended mode employs several calls, and provides a more thorough feedback.
/ask <QUESTION>: Pose a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.

To edit any configuration parameter from configuration.toml, add --config_path=new_value
For example: /review --pr_reviewer.extra_instructions="focus on the file: ..."
To list the possible configuration parameters, use the /config command.

[github-actions]

Summary:

• License scan: failure
• Credentials scan: success
• Vulnerabilities scan: failure
• Unit test: success
• Go linting: success