This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
SOC-CMM: Business Domain - Charter
#1
Can anyone help me better understand the expectation of 3.2.7 Accountability under the Business Domain - Charter? The remarks state "Accountability for the SOC for actions taken". What would you expect a Charter to include regarding "Accountability"? A simple statement on who is ultimately accountable for the SOC (e.g. CISO)? A RACI matrix that defines responsibility and accountability for the various services provided by the SOC?

Thanks in advance. First time working through the SOC-CMM and just looking for input from others.
Reply
#2
Hi,

What is meant with 'accountability' is that you are aware as a SOC (or SOC manager) what you can be held accountable for. A RACI matrix is a great way to define and explain your responsibilities and accountability, especially compare to other teams.

For example: the SOC may be responsible for vulnerability scanning and may be held accountable for time scanning and providing reports and advisores to the organisation. However, follow-up (remediation: patching or applying configuration changes) is actually the responsibility of operational teams within the organisation (and they can be held accountable for timely remediation).

Regards,
Rob.
Reply
#3
Additionally, one can think of SOC's Charter as a Mandate from "above", which is represented by a Responsibility (what they are tasked to take care of/ to do/to be accounted for), and an Authority (what they are allowed/authorised to do).

Sometimes there might be a mismatch: accountability is bigger than the authority required to fulfill the responsibilities, or resources provided are insufficient, thus there might be a conflict. Such situations happen from my experience most often due to lack of precise definitions/clarity in mandate / charter - or strategy/roadmap, how to get to the fulfilment/full coverage of Mandate/Charter (when resources are lacking).

I see objective of this part the SOC-CMM : to identify if this area is clear - that the Charter/Mandate is defined, understood, responsibilities - manageable - i.e. SOC is enabled.

Additional reading might be helpful - https://www.enisa.europa.eu/publications/how-to-set-up-csirt-and-soc (disclosure: I was part of the development team).

Regards,
Vilius Benetis
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)