Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-21752

The server does not set the "Content-Security-Policy" header.

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s: 3.19.1
    • Fix Version/s: None
    • Component/s: Transport
    • Notability:
      4

      Description

      The "Content-Security-Policy" header is designed to modify the way browsers render pages, and thus to protect from various cross-site injections, including Cross-Site Scripting. Insecure values such as '', 'data:', 'unsafe-inline', or 'unsafe-eval' should be avoided. In addition, to protect against Cross-Frame Scripting or clickjacking, it is important to set the 'frame-ancestors' policy with proper values. Insecure values such as '' or 'data:' should be avoided. Setting this value properly is a compliance requirement for most enterprise installations.

       

       Sample Content Security Policy Header:

      Content-Security-Policy: default-src 'self'; frame-ancestors 'self'
      

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            mzeitlin Michael Zeitlin
            Last Updated By:
            Jay Kumar SenSharma Jay Kumar SenSharma
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:
              Date of First Response:

                tigCommentSecurity.panel-title