Let's talk about an example success story of implementing co bit
in this video. We're going to talk about an example of example of Kobe being successfully implemented and the realized benefits of implementing this framework.
So let's start with this example.
An Australian I T consulting firm that works with health care, utility and large government sectors faced a heavily regulated environment.
That's a lot of laws and compliance obligations if we're talking about health care, utility and governmental sectors.
Previously, this firm utilized ISO 27,001 exclusively, which is more of a binary implementation, meaning you either comply or you don't.
It's also not as business focused, which created gaps in the technical application of the standard.
Thus the company faced a challenge.
How could they adopt both Eitel and is a 27,001 which are seemingly competing standards
cope. It gave this I T firm a solution.
This framework allowed the company to address the current state of I T governance.
This framework created a measuring stick, or criteria which the company could compare and evaluate its current state.
From there cope, it was used as a wrapper or container to coordinate the implementation of these different standards.
As cop, it was able to coordinate the implementation of both Eitel and is a 27,001 this Australian firm realize some benefits about Kobe. It
Kobe is a top down approach that is both detailed and can be aligned with the risk appetite of the business.
We've mentioned how Kobe addresses I t risk,
but it can be aligned and tailored to the risk appetite of the business.
How much risk is the business willing to take on
in this case? Probably not much. Given the heavily regulated industries in which this firm operated,
thus cope, it could be customized to orient the business into a more acceptable risk stance.
Kobe is business focused, making it a practical form of I t governance.
It aligns policy to more detailed controls and aligns the cost of controls to the perceived risk.
Let's talk about what that means. If the perceived risk of a certain system that houses sensitive information is high,
the cost of controls may be hired to protect that data.
Alternatively, if you've spent a lot of money on controls to protect information that the business does not need or is relevant. Um, that's a huge waste.
Thus cope. It can be implemented to align the cost of controls to the appropriate risk level so that you're not under spending and under protecting or overspending and over protecting.
As we've said a few times before, Kobe is broad and comprehensive, which is a huge benefit.
So in this video we talked about how co bit combined competing standards into a successful implementation and the benefits found using co bit for an Australian I T consulting firm.