11_Real_World — In the real world — what this looks like in a job

Level: 201 · for anyone who ships systems

Where the previous chapters meet an actual system with an actual owner. The recurring shape: the cryptography is fine and the key management is the entire project — who can read the key, who can rotate it, what happens on a restore from backup, and who is left holding it when someone leaves.

Includes the SAP view, because that is this reader's day job: what the platform gives you (cl_abap_message_digest, cl_abap_hmac, SSF, SNC, the secure store), where it stops, and which decisions are configuration rather than code.

The pages

#	Page	The question it answers	Status
1	Key management	Where does the key live, and who can read it?	planned
2	Cryptography in SAP	What does SAP give you, and what is left to you?	planned

Every page above is a plan until its row says written; see ROADMAP.md.

The through-line

Encryption at rest protects against a stolen disk and almost nothing else. Naming the threat a control actually addresses is most of the value you can add in a design review.