Skip to content

Conversation

@labkey-jeckels
Copy link
Contributor

Rationale

Let's keep track of the Content Security Policies that are in use

Changes

  • Two new metrics, tracking the templated CSPs deployed: modules.API.contentSecurityPolicy.enforce and modules.API.contentSecurityPolicy.report

@labkey-adam
Copy link
Contributor

I've added similar metrics in my PR: #6359

I'm including only CSP version, but I could easily add the full CSP. At a minimum, let's get my PR merged and iterate on that.

@labkey-jeckels
Copy link
Contributor Author

I've added similar metrics in my PR: #6359

I'm including only CSP version, but I could easily add the full CSP. At a minimum, let's get my PR merged and iterate on that.

Great, thanks for the note. I won't do anything with this PR for the moment. Ultimately, I'm hoping for an approach that helps us understand which on-premise deployments have a CSP too.

@labkey-adam
Copy link
Contributor

I've added similar metrics in my PR: #6359
I'm including only CSP version, but I could easily add the full CSP. At a minimum, let's get my PR merged and iterate on that.

Great, thanks for the note. I won't do anything with this PR for the moment. Ultimately, I'm hoping for an approach that helps us understand which on-premise deployments have a CSP too.

Yep, me too. I'll look at adding the full CSP to my thing and we can go from there. Feel free to review, if you want.

@labkey-jeckels labkey-jeckels deleted the fb_cspMetric branch February 25, 2025 01:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants