Skip to the content ForoHackers
Log inJoin

Application security: start here

Application security
#757 · Ophuscado · · Report

Application security is the practice of building software so that it keeps working when someone sends it input its authors did not expect. It covers design, code, dependencies and deployment, and it matters because most breaches begin with an ordinary flaw in an ordinary program rather than with anything exotic.

Key concepts

  • Threat modelling: before writing code, ask what you are protecting, from whom, and where trust changes hands.
  • Input handling: everything from outside is untrusted; validate it, encode it for where it lands, and never build commands or queries by pasting strings together.
  • Authentication and authorisation: who is this, and what may they do; check on the server, on every request.
  • Least privilege: each component gets only the access it needs, so a flaw stays small.
  • Defence in depth: several independent layers, so one mistake is not the end.

Vocabulary

  • Vulnerability: a flaw that can be abused to break a security property.
  • Attack surface: every place where outside data or users reach the program.
  • SAST and DAST: analysing source code, and testing the running application.
  • CVE: a public identifier for a known vulnerability.

What to study, in order

  1. How one real application is built: its inputs, its data stores, its users and its trust boundaries.
  2. A threat model of a small project of your own, drawn as a data-flow diagram.
  3. The common flaw classes in the OWASP lists, each reproduced and then fixed in a deliberately vulnerable practice app that you run yourself.
  4. Parameterised queries, output encoding and a sound session design, implemented by hand once.
  5. Static analysers, dependency scanners and code review checklists in your own build pipeline.

Related tags

#secure-coding #web-security #vulnerability-research #supply-chain-security #identity

Log in or join to reply.