Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Penetration Testing: Cacheable HTTPS #669

Open
JennaySDavis opened this issue Aug 8, 2024 · 2 comments
Open

Penetration Testing: Cacheable HTTPS #669

JennaySDavis opened this issue Aug 8, 2024 · 2 comments

Comments

@JennaySDavis
Copy link
Contributor

Description from Penetration Testing:
Application browser may store a local cached copy of content received from web servers including sensitive content accessed via HTTPS. Sensitive information in the application responses can be stored in the local cache which can be retrieved by other users who have access to the same computer at a future time.

@JennaySDavis JennaySDavis changed the title Cacheable HTTPS Penetration Testing: Cacheable HTTPS Aug 8, 2024
@JennaySDavis
Copy link
Contributor Author

The findings stated below were reported to ISSO and ISSM on 8/2/24:

Vulnerability: Cacheable HTTPS

Severity: Low

Site(s): https://889.smartpay.gsa.gov/#/ and https://smartpay.gsa.gov/

Penetration Test Report Recommendation: Update the response header on all responses containing sensitive information to not cache.

Findings: Neither the SmartPay Program site nor the 889 Tool contains sensitive data. All pages are public and accessible to everyone. The recommendation is not to make any application changes, as allowing the user's browser to cache helps with user experience and performance, so they don't always have to go to the server when accessing the pages.

@JennaySDavis
Copy link
Contributor Author

  • Per Debra Smith, the Penetration Test team has closed the penetration test finding and she has marked this item as 'Closed' on the POA&M.

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

No branches or pull requests

1 participant