GeekInTheNorth / GeekInTheNorth/Stott.Security.Optimizely
[CSP] Add the ability to mark a violation as resolved / or ignored
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 11
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
The Content Security Policy - Violations screen does not have a mechanism that allows you to filter out violations that have already been resolved. When a Site is Launched, there are often hundreds of violations as the CSP is configured and this can make it hard to understand what has been processed. By adding a mechanism to ignore or mark a violation as resolved would help the management of this list.
Entry points to consider here:
- When adding a source manually within the sources list, matching violations should be set to resolved
- When converting a violation into a source, mark the violation as resolved
- Add an "Ignore" option to violations
- Add the ability to filter by:
- All - Shows all violations
- Pending - Shows violations which have not been marked as solved or ignored
- Ignored
- Solved
Contributor 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.
Research direction
Start at the Content Security Policy Violations screen and review the linked Violations Discussion. Trace the listed entry points: adding a source manually, converting a violation into a source, adding Ignore, and filtering by All, Pending, Ignored, and Solved. Done means violations can be resolved or ignored and the four filters show the corresponding states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100