Skip to content

Chapter 6 of 7

Application, Cloud, and Development Security

Applications are a primary battleground, and the OWASP Top 10 is the most widely cited list of critical web application security risks, including broken access control, cryptographic failures, and injection flaws. Secure coding practices address these at their source. Input validation checks that user input conforms to expectations before processing, output encoding encodes data before it is rendered to defeat injection attacks, and parameterized queries ensure that database statements cannot be hijacked by malicious input. Cookies carry authentication state and must be protected with HttpOnly, Secure, and SameSite flags to mitigate XSS theft, eavesdropping, and cross-site request forgery. Security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options add browser-side defenses against content injection, downgrade attacks, and clickjacking.

Automated testing helps catch vulnerabilities before release. Static Application Security Testing (SAST) analyzes source code for vulnerabilities, Dynamic Application Security Testing (DAST) tests running applications from the outside, Interactive Application Security Testing (IAST) combines both views, and Software Composition Analysis (SCA) checks third-party dependencies for known flaws. These tools support DevSecOps, which integrates security into DevOps practices throughout the development lifecycle, and the principle of shift-left security, which addresses security earlier in the design and coding phases. A Software Bill of Materials (SBOM) provides an inventory of components in a piece of software, helping organizations respond when new supply chain vulnerabilities are disclosed.

Cloud introduces its own model and tooling. Under the shared responsibility model, the cloud provider secures the underlying cloud while customers secure their data and configurations within it. Cloud services are commonly described as Software as a Service (SaaS), Platform as a Service (PaaS), or Infrastructure as a Service (IaaS). Cloud Security Posture Management (CSPM) finds misconfigurations across cloud environments, and Cloud Workload Protection Platforms (CWPP) secure workloads running there. Containerized applications built with Docker and orchestrated by Kubernetes bring additional concerns around image integrity, secrets, and network policies. Endpoint security protects laptops, phones, and servers, often augmented by Mobile Device Management (MDM) to handle Bring Your Own Device (BYOD) scenarios, while awareness of shadow IT (systems used without organizational approval) closes a common visibility gap.

All chapters
  1. 1Foundations of Cybersecurity
  2. 2Threats and Attack Vectors
  3. 3Cryptography and Secure Communications
  4. 4Identity and Access Management
  5. 5Security Architecture and Network Defenses
  6. 6Application, Cloud, and Development Security
  7. 7Operations, Incident Response, and Governance

Drill it

Reading is not remembering. These come from the Cybersecurity Fundamentals deck:

Q

What is cybersecurity?

The practice of protecting systems, networks, and data from digital attacks, unauthorized access, and damage.

Q

What is the CIA triad?

Confidentiality, Integrity, and Availability — the three core security principles.

Q

What is confidentiality?

Ensuring information is accessible only to authorized parties.

Q

What is integrity (security)?

Ensuring data is accurate and unaltered except by authorized changes.