Scenario 3 - Attacker doc update
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure, kubernetes
- Domain
- documentation, security
Research direction
Locate the documentation for Scenario 2 and Scenario 3, then read the transition covering defender actions and Entra ID enablement. Clarify why access remains possible at the start of Scenario 3, and verify that the updated narrative matches the scenario sequence.
Written by the indexing model from the issue text.
Description
Document needs to clarify the story between Scenario 2 (defender) / enablement of Entra ID and how access is still possible at the start of Scenario 3.
- Dominant language
- Shell
- Stars
- 10
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/aks-ctf
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug priority-medium to-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
WordPress/Documentation-Issue-Tracker#2540 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
dsx-ai-factory/infra-controller#8301 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100