HTTP Security


  • httpOnly
  • enable secure flag
  • make them expirable
  • activate SameSite to avoid cookie leaving the browser unless the current page origin matches the target
  • avoid persistent cookies

HTTP Request Headers

  • the Referrer is the website where the req comes from. This can leak GET querystring. Even in https, it can be cached, bookemarked, etc
  • uses method="GET" by default
  • never put sensitive data on the URI (querystring)
  • don't trust user-agent
  • detect and block certain browsers: validate and whitelist user agents and browsers versions.. notify if any case like that happens and notify the security team, specially in intranet. Prevent webscrapping, malware, and hacking. block webTV since doesn't support https
  • use html rel="noreferrer"
  • use redirect interstitial popup to clean referer and other data
  • count-block the failed login attempts to prevent bruteforce. Track per userName, not cookie or other thing.

HTTP Response Headers

  • don't leak the server information eg. powered by Express v4. Also don't post it on the job descriptions. or lie about the powered by to catch hackers. Hackers can figure out the server type through server-fingerprinting.
  • use honeytoken inputs and hidden params to detect hackers


  • protects from clickjacking

results matching ""

    No results matching ""