Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Triage Security Findings - Defender Initial Score #858

Open
Tracked by #826
ExpressDead opened this issue Nov 19, 2024 · 2 comments
Open
Tracked by #826

Triage Security Findings - Defender Initial Score #858

ExpressDead opened this issue Nov 19, 2024 · 2 comments
Assignees
Labels

Comments

@ExpressDead
Copy link

ExpressDead commented Nov 19, 2024

Hold a meeting to triage initial security findings in the most "production like" environment your code will be deployed into. Address the relevant findings using Defender for Cloud recommendations or using the customer's tooling. Create backlog items as needed.

ACTIONS

Hold a triage meeting to review security recommendations.
Address recommendations, create backlog items to remediate findings as appropriate.
Record the observed Defender score here.

@ydaponte
Copy link
Collaborator

@ExpressDead - as a best practice we are adding a DoD for all User stories and tasks. Can you also define the DoD on all the tasks you've added to the backlog please? Thank you!

@ydaponte ydaponte assigned jayce21-ms and unassigned ExpressDead Dec 12, 2024
@jayce21-ms
Copy link

Update:

The initial Defender Score should be based on the security findings from the environment where the production code is deployed.

DoD:

Triage the initial security findings
Review Defender Recommendations to prioritize mitigations
Create backlog items to remediate as appropriate.
Record current Defender Score (repeat for each Sprint or Milestone until completion)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants