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

Secure the ExpressJS middleware #11

Open
damianperera opened this issue Oct 18, 2017 · 0 comments
Open

Secure the ExpressJS middleware #11

damianperera opened this issue Oct 18, 2017 · 0 comments

Comments

@damianperera
Copy link
Contributor

damianperera commented Oct 18, 2017

Secure and harden the ExpressJS middleware. Third-party modules can be used. The following security features need to be covered.

  • Content-Security-Policy header for Cross-Site Scripting (XSS) attacks
  • Expect-CT header for Certificate Transparency
  • X-DNS-Prefetch-Control header to control browser DNS prefetching
  • X-Frame-Options header to prevent clickjacking attacks
  • Remove the X-Powered-By header to prevent hackers from exploiting vulnerabilities in Express and Node
  • Public-Key-Pins header to prevent person-in-the-middle attacks
  • X-Download-Options header to prevent IE from opening untrusted HTML files
  • Cache-Control, Surrogate-Control, Pragma and Expires headers to prevent users from getting cached versions of your files
  • X-Content-Type-Options header to prevent browsers from trying to guess the MIME type, which can have security implications
  • Referrer-Policy header to prevent knowing where a user is referred from
  • X-XSS-Protection header to prevent reflected XSS attacks
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