CybersecurityOffensive Security

Runtime Application Self-Protection

Overview

Direct Answer

Runtime Application Self-Protection (RASP) is an in-process security technology that protects applications from attacks by monitoring and controlling application behaviour during execution. It detects malicious requests, unsafe method calls, and exploitation attempts in real time, then blocks or logs them without requiring external security infrastructure.

How It Works

RASP operates by instrumenting application code or integrating with runtime environments to observe method invocations, data flows, and user inputs. When suspicious patterns—such as SQL injection payloads, buffer overflow attempts, or unauthorised file access—are detected against configurable security rules, the engine halts execution or sanitises the request before it reaches vulnerable code paths.

Why It Matters

Organisations adopt RASP to reduce mean time to detection and response for zero-day and known vulnerabilities, particularly in legacy systems where patching is delayed. It provides visibility into actual attack traffic without network-level inspection, enabling faster incident response and stronger compliance postures for regulated industries.

Common Applications

RASP is deployed in web applications, microservices, and Java/.NET environments where organisations need protection during the software development lifecycle. Financial institutions, healthcare providers, and e-commerce platforms use it to defend applications against injection attacks, cross-site scripting, and insecure deserialisation.

Key Considerations

RASP introduces performance overhead due to inline monitoring and may generate false positives if security policies are misconfigured. Tuning is essential to balance protection efficacy with application responsiveness, and it does not replace code review or secure development practices.

Cross-References(1)

DevOps & Infrastructure

More in Cybersecurity

See Also