Risk appetite is a boundary, not a mood. A compliance program needs to know which exposures can be accepted by the process owner, which need extra controls, and which require executive or board-level acceptance. The boundary should be visible before the exception arrives. The practical pattern is: category, threshold, evidence, owner, action. For example: "Customer data may not move to a new processor until due diligence is complete and the DPA is signed; exceptions require Privacy, Security, and Legal approval." That sentence is more useful than "we are cautious about privacy." Why it works Appetite speeds decisions because it narrows…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in