In order to give them some coherence, I've organized them into a sample compliance program based around information security.
Here's what I have for you so far.
Key Considerations
- Frequent “top-ups”, to help keep the information fresh. There’s something happening every month. This also reinforces that information security is an ongoing activity, not a “one and done” event.
- Quick hits. Although there’s something happening every month, none of it is long.
- Real KPIs (Key Performance Indicators), based on information security red flags and actual incidents, not on vanity metrics (such as course completions or test scores).
- Real-world tests, because life doesn’t ask you multiple-choice questions.
- A course, but not always, not for everybody, and not necessarily all of it (more on this later).
- As needed, if needed support elements.
- Story-based delivery. The "When Spies Attack" series illustrates information security concepts in a narrative-driven manner.
- Variety. Some years “When Spies Attack” will be a comic, other years it’ll be a podcast, maybe it's an episodic game another year.
