11.07.2015 Views

Cyber Security Capability Framework & Mapping of ISM Roles - agimo

Cyber Security Capability Framework & Mapping of ISM Roles - agimo

Cyber Security Capability Framework & Mapping of ISM Roles - agimo

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

PART 2Australian Government Information <strong>Security</strong> ManualThe second part <strong>of</strong> the project was mapping <strong>of</strong> the Chief Information <strong>Security</strong> Officer, IT<strong>Security</strong> Manager and IT <strong>Security</strong> Officer roles from the Australian Government Information<strong>Security</strong> Manual (<strong>ISM</strong>) to the competencies originally in the DeCAF, now embedded into the<strong>Cyber</strong> <strong>Security</strong> <strong>Capability</strong> <strong>Framework</strong>.The <strong>ISM</strong> provides a framework that enables agencies to address both new and existingsecurity risks to systems. The manual sets down minimum requirements for informationsecurity and describes a number <strong>of</strong> roles within the security environment. These include thethree roles outlined for mapping:The target audience for this manual is information security practitioners within, or contractedto, an agency. This includes, but is not limited to:• security executives / chief information security <strong>of</strong>ficers (CISOs)• agency security advisors (ASAs)• information technology security advisors (ITSAs)• information technology security managers (ITSMs)• information technology security <strong>of</strong>ficers (ITSOs), and• infosec-registered assessors.The roles in the manual are described in terms <strong>of</strong> the context, risks and controls that shouldbe accounted for within the roles plus a rationale for appointing each <strong>of</strong> the roles.<strong>Mapping</strong> <strong>of</strong> the rolesAt the original workshop validating the DeCAF competencies mapped onto the APSC ICTCapabilities, workshop participants reported high consensus that the DeCAF documentdescribed competencies up to and including the EL2 level <strong>of</strong> classification. Therefore, theresultant <strong>Cyber</strong> <strong>Security</strong> <strong>Capability</strong> <strong>Framework</strong> did not extend to the SES level.Upon examination <strong>of</strong> the roles, it was noted that the Chief Information <strong>Security</strong> Officer roleshould be appointed at the Senior Executive Service level and is described as beingresponsible for co-ordination <strong>of</strong> security at a strategic level within the agency. Due to thehigh classification level <strong>of</strong> this role, it was decided that the role would not be mapped againstthe <strong>Capability</strong> <strong>Framework</strong>.The remaining three roles, the IT <strong>Security</strong> Advisor, the IT <strong>Security</strong> Manager and the IT<strong>Security</strong> Officer were mapped at the EL2 and EL1 levels. This process involved examination<strong>of</strong> the responsibilities <strong>of</strong> each role as set out in the <strong>ISM</strong> and comparison <strong>of</strong> these with thosecompetencies previously mapped to the <strong>Cyber</strong> <strong>Security</strong> <strong>Capability</strong> <strong>Framework</strong>. Areas <strong>of</strong>overlap were noted and duplication avoided. Where new competencies were identifiedthese were included in the final mapping.As noted in Part 1, this document was then sent out for comment and feedback as part <strong>of</strong>the final consultation round <strong>of</strong> the <strong>Cyber</strong> <strong>Security</strong> <strong>Capability</strong> <strong>Framework</strong>. Feedback receivedwas incorporated into the final versions <strong>of</strong> the mapped roles which are presented below.Produced for AGIMO by Workplace Research Associates Pty Ltd 2010 Page 16

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!