HTTP Security headers not enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard Charm |
Fix Committed
|
Wishlist
|
Erhan Sunar |
Bug Description
The following HTTP Security headers were not identified during a security scan and could be enabled
to further increase security:
• Cacheable HTTPS Response - Unless directed otherwise, browsers may store a local cached
copy of content received from web servers. Some browsers, including Internet Explorer, cache
content accessed via HTTPS. If sensitive information in application responses is stored in the
local cache, then this may be retrieved by other users who have access to the same computer
at a future time.
RECOMMENDATION:
Applications should return caching directives instructing browsers not to store local copies of any
sensitive data. The Web Server should return the following header:
Cache-control: no-store
Pragma: no-cache
Changed in charm-openstack-dashboard: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
information type: | Private Security → Public |
Changed in charm-openstack-dashboard: | |
assignee: | nobody → Erhan Sunar (esunar) |
status: | Triaged → In Progress |
Changed in charm-openstack-dashboard: | |
status: | In Progress → Fix Committed |
Subscribed field-medium as this is a commercial requirement, for a site running Bionic/queens.