Professor Franklin
Accessibility settings

Preferences are saved in this browser when storage is available.

Chapter 6 · Reading 4 of 6

Web Application Security

Security+ SY0-801 · Objectives 4.1

Return to the room calendar. The service uses encrypted transport and sits behind a filtering gateway. A student can nevertheless see another student’s private booking details. To choose a fix, follow one request to the place where ownership of the record is known.

Web application security involves protecting web applications from security threats and vulnerabilities. It encompasses a range of practices, tools, and technologies designed to safeguard applications from attacks that could compromise data, disrupt services, or provide unauthorized access to resources.

  • Authentication and Authorization
  • Data Encryption
    • In Transit: Encrypting data as it travels between the client and server using protocols like TLS/SSL.
    • At Rest: Encrypting stored data to protect it from unauthorized access.
  • Input Validation
  • Session Management

Common Threats

Injection Attacks: Attacks where malicious code is inserted into a program or query.

Cross-Site Scripting (XSS): Injecting malicious scripts into web pages viewed by other users.

  • Defense: Apply context-appropriate output encoding when rendering user content.

Cross-Site Request Forgery (CSRF): Forcing a user to execute unwanted actions on a web application in which they are authenticated.

  • Example: Submitting a form on behalf of the user without their consent.

Web Application Firewalls (WAF) Web Application Firewalls (WAFs) are crucial for protecting web applications from a wide range of threats. By filtering and monitoring HTTP/HTTPS traffic, WAFs help prevent attacks such as SQL injection, XSS, and CSRF. With different deployment options, WAFs offer flexibility and enhanced security for web applications, making them an essential component of a robust security strategy.

Assigning controls to layers

Secure cookies restrict how a browser sends and exposes a session identifier. A web application firewall can filter recognizable unwanted requests at the edge. The application still owns record-level authorization and input handling. Verify each control with an expected allowed case and a denied case using synthetic records.

Try the same operation with two identities

Create two synthetic reservations with distinct owners. Define the expected result for the owner, another ordinary student and an authorized scheduler. Test reading and modifying the record separately. It is easy to protect an edit button while leaving a download or calendar export too broadly available. Confirm the server-side result and the audit event for each role.

The useful handoff to a developer includes the resource, the permitted relationship and the observed decision. “Only the owner or assigned scheduler may read the private notes” can become a test and an acceptance criterion. Once a corrected build passes those checks, the team still needs assurance that the artifact reaching production is the one that passed review.

Request inspection stack

Inspect the three records, then use the evidence to answer the question.

1. Transport

TLS protects data in transit.

Transport encryption is active

2. Application

Enforce authorization on each resource.

Edge filter accepts a well-formed request

3. Edge filtering

A WAF provides additional inspection.

User requests another student's private record

Apply the reading

Why does an authenticated session still need an authorization check when opening an invoice?

Compare your reasoning

The session identifies the user. The application must establish that this user may access this invoice.