oracuk / oisru Goto Github PK

Thought this example of Intel having to publish their earning statement early (FT.com) because it had been leaked from their PR website was an interesting example of the Compliance/Strategic consequences of damaged regulator relations and damaged investor relations respectively.

We may wish to include examples of various types of consequence to bring the Universe to life?

Label: Feature request :-)

I'm looking at some examples to articulate common risk scenarios and uses of OISRU.

One common scenario is around the service unavailability event that can, naturally, have many sources. For example:

• Criminal or hacktivist are sensible sources for DDoS-type scenarios
• Compromised supplier is suitable for a supplier outage (e.g. ISP failure)

For a 'wear and tear' or 'component failure' type scenario, my thinking is that the source of this is ineffective internal on the basis that proactive maintenance is required for any machinery/hardware/software/service.

It is, perhaps, a little unfair in the event of a manufacturing defect were failure occurs significantly before the Mean Time Between Failures. Though defects could be considered compromised supplier. (And, hopefully, they may not occur anywhere nearly frequently enough to warrant serious inclusion in the identified risk scenarios.)

Do we consider the current source lists sufficient to cover these type of 'wear and tear' scenarios?

Does anyone see value in mapping the consequences on Risk Consequence page to FAIR's six forms of loss? Additional column?

If so, I'd be willing to take a first pass at it.