GeekInTheNorth / GeekInTheNorth/Stott.Security.Optimizely

[CSP] Add tool for clearing down CSP Violations

Open
#381 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Under Consideration
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 purge all violations. 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 clear down CSP violations, the list can be built fresh based on what is still outstanding.

See Violations Discussion

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Content Security Policy - Violations screen and read the linked Violations Discussion for the expected clearing behavior. Trace how violations are displayed and persisted, then define done as providing a way to purge all current violations so the list can be rebuilt from newly reported items.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.