120 likes | 124 Views
Learn how to tailor the OCTAVE methodology at Maricopa Community Colleges to effectively manage security risks. This approach enhances overall effectiveness, accountability, and compliance with applicable laws and regulations.
E N D
Ways to Fit Security Risk Management to Your Environment Using the OCTAVE Methodology Tailoring OCTAVE at Maricopa Community Colleges Carol A. Myers, CISSP Director College Technology
Maricopa Integrated Risk Assessment(MIRA) • Enterprise Risk Management • Integrated risk framework • Not just “insurable” risks • Collaboratively identify, asses, manage future risks and opportunities individually and across the organization
Charge From the Chancellor • Multi-year implementation plan • Identified specific outcomes • Increased overall effectiveness and accountability • Sound business process; greater assurance of business continuity • Clear demonstrated compliance with applicable laws & regulations • Enhanced employee empowerment & pride • Reinforcement of the strong MCCCD cultural identity • Enhanced competitive advantage
Why OCTAVE? • Institutionally inclusive (Organizational View) • Assets • Threats • Organization (not just IT) vulnerabilities • Current security requirements
Why OCTAVE? • It’s the technology too • Current inventory • OS level • current patch methodology, tracking, auditing • services enabled – disabled why • Application level • Security tools
Why OCTAVE? • Strategize and Plan • Manage risks and Opportunities • Protect and Review plans • Mitigation strategies now and for the Future • It’s never just about the technology
So, how’d it work? • Maricopa-wide risk initiative (MIRA) • OCTAVE adapts best with enterprise risk management methodology, senior level buy-in and support • IT Security RA work done through subgroup of MIRA committee • Auditor, faculty member, college administrative dean, general counsel, HR director, risk manager and IT security director
Why Not Just Use OCTAVE As Is? • Narrowed focus primarily to operational risks and security practices • MIRA methodology supports chief-level buy-in • Technology examined only in relation to good security practices (catalog) • Protection decisions based on confidentiality, integrity and availability (for IT staff)
Four Simple Phases • System infrastructure analysis and documentation (IT staff) • Risk and opportunity identification (IT staff) • Mitigation strategies and costs, with management • Asset cost analysis, with management
Stop the Babble • Primarily forms driven • Checkboxes • Short answer • Maricopa forms are heavily OCTAVEFIED • OCTAVE forms make sense • OCTAVE forms are initially easy to understand and fill out
Now What? • System-wide adoption of pilot • Can easily adapt to another college’s needs given the narrowed focus • Supports and reinforces the MIRA model • Encourages risk awareness
Contact Information Carol Myers Paradise Valley Community College 18401 N. 32nd Street Phoenix, AZ 85032 602.787.7788 carol.myers@pvmail.maricopa.edu