liveBook · Manning

Shield right

As explained in Secure APIs

A security approach that emphasizes protecting APIs after they have been released.

Shield right protects APIs after release by emphasizing operational defenses such as configuration, secrets management, rate limiting, versioning, logging, monitoring, and threat detection. It complements earlier security work by addressing risks that emerge in deployed systems. section 1.1

Apply the approach as a practical security loop:

  • Identify attack vectors, including API input parameters. section 1.1
  • Model the threats and consider their possible consequences. section 1.1
  • Harden the API with measures that prevent or mitigate the attacks. section 1.1
Figure 1.2 To secure our APIs, first, we identify attack vectors, such as the API input parameters. Then, we model the possible threats. Finally, we harden our API by applying measures that prevent or mitigate those attacks.
figure

A visual workflow connects attack-vector identification, threat modeling, and API hardening. section 1.1

How Secure APIs covers it

How deep it goes
Defines a security framework and workflow but defers detailed observability and infrastructure practices to later treatment.
Examples
Uses API input parameters as attack vectors and illustrates the workflow with security-axis and hardening figures.
What you can do after
Operate/configure released APIs by identifying attack vectors, modeling threats, and applying preventive or mitigating controls.
How it connects
Connects API security with shift left, threat modeling, observability, rate limiting, secrets management, and infrastructure security.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Secure APIs. The section links point to the parts of the book it draws on.