Prevent sensitive data: Difference between revisions

From bibbleWiki
Jump to navigation Jump to search
No edit summary
Line 37: Line 37:
**Outbound,cryptography and auditing code
**Outbound,cryptography and auditing code
*Data at rest, files or software
*Data at rest, files or software
==OWASP Recommendations==
*Keep sensitive data out of the URL
*Use TLS everywhere
**Never rely on network access control
**All authenticated pages should be on TLS
*Strong Procotols
**Never use SSL 1,2 or 3
**Use strong ciphers

Revision as of 04:54, 4 September 2020

Sensitive Data

Sensitive Data is the set of data that contains elements from user data, application data and data protecting data such that user data is not exposed to unauthorized parties

  • Application Data
    • Configuration Data
    • Logging Data
    • Application Data
  • User Data
    • Personal Information
    • Personal Identification Information, drivers license
  • Data Protecting Data
    • Cryptokey
    • Passkeys
    • Access Control lists

Just because it can contain sensitive data, it does not mean it is. Controls can be put in place to manage it such as in development or via business process.

  • Not all user data
  • Logging files

Data Classification can be by either

  • Laws, GDPR, PCI DSS, can include but not exclusive to
    • Personal data, trade union membership, genetic, bio metric, health data
  • Business requirements

Attacks

OWASP Scope

The OWASP scope includes

  • External attacks only
  • Two extremes of user types
    • Anonymous users
    • Highly Privileged users

Web Applications

Attacks can happen

  • Connection between browser and app
  • Connection between app and DB
  • Database or database management system
  • Web browser

Categories of Attack can be

  • Data In-transit, connections
    • Inbound, code that does authentication, authorization, validation or logging
    • Outbound,cryptography and auditing code
  • Data at rest, files or software

OWASP Recommendations

  • Keep sensitive data out of the URL
  • Use TLS everywhere
    • Never rely on network access control
    • All authenticated pages should be on TLS
  • Strong Procotols
    • Never use SSL 1,2 or 3
    • Use strong ciphers