Skip to content

Research desired CSP for serverless offering #158015

Open

Description

We should audit the available CSP options against our current policy, and identify which, if any, we should consider adding/altering to the serverless offering. If these changes don't break the classic offering, then they should be applied there, too.

The output of this issue is:

  • Identify the initial CSP we wish to ship with the serverless offering, with a technical design of how we will implement these changes.
  • Identify the ideal CSP we wish to eventually ship with both the serverless and classic offerings. A technical design isn't required for this, but we should be able to justify why this won't be a part of the initial serverless offering.

The initial and ideal CSP may be identical, and that is fine. The purpose of this task is to understand the available options, and which of them are applicable to Kibana.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

Feature:HardeningHarding of Kibana from a security perspectiveFeature:Security/CSPPlatform Security - Content Security PolicyProject:ServerlessWork as part of the Serverless project for its initial releaseTeam:SecurityTeam focused on: Auth, Users, Roles, Spaces, Audit Logging, and more!

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions