Use of the COBIT Security Baseline

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    Favorites, Groups & Events

    Use of the COBIT Security Baseline - Presentation Transcript

    1. COBIT Barry Caplin Chief Information Security Officer Minnesota Department of Human Services Christopher Buse Information Technology Audit Manager Minnesota Office of the Legislative Auditor
    2. Agenda
      • Need for an Information Security governance framework
      • COBIT Framework overview
      • Use of COBIT in the audit process
      • Use of the COBIT Security Baseline at DHS
    3. About Us
      • Barry Caplin
        • CISO for DHS
        • Member of ISACA, ISSA, InfraGard
        • CISSP, CISA, CISM, ISSMP
      • Christopher Buse
        • IT Audit Manager for OLA
        • Active in ISACA
        • CPA, CIA, CISA, CISSP
    4. Information Security Governance Why Adopt a Framework?
    5. Information Security Governance
      • “ a framework to provide assurance that information security strategies are aligned with business objectives and consistent with applicable laws and regulations” – www.isaca.org
      • Regulations – HIPAA, MGDPA, IRS, SSA, etc.
      • Establish a program
      • Based on Standards, Industry Best Practice
    6. Information Security Governance
      • With Information Security Governance:
      • information security strategy supports business
      • senior management supports information security
      • defined roles and responsibilities
      • reporting and communication
    7. Information Security Governance
      • With Information Security Governance:
      • regulatory issues and impact understood
      • information security policies support business goals and objectives
      • procedures and guidelines support information security policies
      • Happiness is sure to follow!
    8. Information Security Governance
      • Without Information Security Governance:
      • unclear security strategy inconsistently supports business
      • senior management can’t understand or support information security
      • Ad hoc roles and responsibilities
      • Lack of reporting and communication
    9. Information Security Governance
      • Without Information Security Governance:
      • JIT:
      • regulatory compliance efforts
      • information security policies
      • Out of sync with business
      • Surprises
      Conflict
    10. Information Security Governance Who needs Security Governance? We do!
    11. Industry Best Practice
      • What do we need?
      • Established and Proven methodology
      • National or International acceptance
      • Ability to Measure/Audit
    12. The 10000 Foot View Information Security Governance Hierarchy Information Lifecycle Management Compliance Information Policy Information Risk Management Information Security Governance Framework
    13. COBIT What’s it all About?
    14. What is COBIT
      • C ontrol Ob jectives For I nformation and Related T echnology
      • Governance framework
        • Collection of controls that should be done at various levels in an organization
        • Outline of what must be done, not how
      • Supporting toolset
        • Management
        • Auditors
    15. Strengths
      • Outstanding support
      • Incorporates work done by many others
      • Business focused
      • Publicly available
    16. Support
      • Overseen by the IT Governance Institute
        • Nonprofit and vendor neutral
        • Heavily supported
        • Well represented by industry, academia, & government
      • COBIT R&D managed by a Steering Committee
        • Core team and working groups worldwide
        • Many expert reviewers
        • User feedback
      • Now in 4 th edition
    17. Information Sources
      • Over 40 recognized standards and best practices
      • Sources underlying version 4.0 changes
        • Committee of Sponsoring Organisations of the Treadway Commission
          • Internal Control—Integrated Framework, 1994
          • Enterprise Risk Mangement—Integrated Framework, 2004
        • Office of Government Commerce, IT Infrastructure Library, 1999-2004
        • ISO/IEC 17799, Code of Practice for Information Security Management
        • Software Engineering Institute
          • SEI Capability Maturity Model, 1993
          • SEI Capability Maturity Model Integration, 2000
        • Project Management Institute, Project Management Body of Knowledge
        • Information Security Forum, The Standard of Good Practice for Information Security, 2003
    18. Business Focus
      • IT resources must be
        • Managed through standard processes
        • To meet business requirements
      • Metrics and maturity models to measure performance
      • Responsibilities of business and IT process owners identified
    19. COBIT Framework
      • 34 processes, grouped into 4 domains
        • Plan and Organize
        • Acquire and Implement
        • Deliver and Support
        • Monitor and Evaluate
      • Handout: P07 Manage IT Human Resources
    20. Products
      • Framework
        • Control Objectives
        • Control Practices
        • Management Guidelines
      • Assurance
        • IT Assurance Guide
        • Control Objectives for SOX
      • Governance
        • Implementation Guide
        • Quickstart
        • Security Baseline
        • Board Briefing
    21. Cost
    22. Still Interested
      • Visit the COBIT Website
        • http://www.isaca.org
      • Watch our local ISACA chapter for training opportunities
        • http://www.mnisaca.org
    23. COBIT as an Audit Tool Use of the COBIT Framework in the Office of the Legislative Auditor
    24. Planning
      • COBIT Summary Table used to scope projects
        • Audit Focus: Data integrity and confidentiality
        • Question: What control processes have a primary or secondary impact
    25. Reporting
      • Criteria used to help draft report comments
      • Discussions about issue severity follow maturity model format
    26. COBIT as a Management Tool Use of the COBIT Security Baseline at the Department of Human Services
    27. MN DHS
      • Mission - helps people meet their basic needs so they can live in dignity and achieve their highest potential
      • Consumers include:
        • seniors who need help paying for hospital and nursing home bills or who need home-delivered meals
        • families with children in a financial crisis
        • parents who need child support enforcement or child care money
        • people with physical or developmental disabilities who need assistance to live as independently as possible
    28. MN DHS
      • Direct service through
      • DHHS – Deaf and Hard of Hearing Services
      • SOS – State Operated Services includes
        • RTC’s – Regional Treatment Centers, including St. Peter, Moose Lake
        • Forensics – St. Peter, Moose Lake, METO (MN Extended Treatment Options)
        • State-run group homes
        • New community-based treatment centers
        • State-run nursing home – Ah-Gwah-Ching
    29. MN DHS
      • Administrations (Divisions)
      • CFS – Children and Family Services – Child Support Enforcement, Endangerment, Social Services, Medical/Welfare Eligibility
      • Chemical and Mental Health Services– including SOS
      • Health Care Administration and Operations
      • Continuing Care
      • FMO – Finance and Management Operations – including Information Security, IT
    30. MN DHS
      • Programs are state-administered, county-delivered
        • Including MinnesotaCare, Medical Assistance, General Assistance Medical Care, mental health services, alternative care services, chemical dependency services and regional treatment center services
      • One of the largest state agencies
      • 2500 CO, 5000 SOS distributed staff
      • State and Federal funding
    31. COBIT Use in State
      • Chosen by CISO/Security Domain team for statewide security implementation
      • Separate agency implementation
      • Additional technical standards chosen: PCI, OWASP
    32. COBIT and Security
      • COBIT Security Baseline
      • Includes mapping to ISO17799
      • Guide for DHS implementation
      • Identifies 39 “steps” (high-level projects)
      • Multiple sub-projects
    33. Maturity Model
      • Measure the maturity of the team/unit/organization to the high level control objectives. Are the processes:
      • 0 – non-existent
      • 1 – Initial/Ad-Hoc
      • 2 – Repeatable but Intuitive
      • 3 – Defined Process
      • 4 – Managed and Measurable
      • 5 – Optimized
    34. Initial Baseline
      • Assess maturity of DHS Body of Policy and ISS projects and implementation using Maturity Model
        • Self rating - ISS
        • “ inner circle” units – central IT, MSD
        • Business customers – HCO, CFS, SOS, etc.
    35. Implementation Steps
      • Review initial maturity assessments
      • Gap analysis
      • Selection of initial metrics
      • Prioritization of Phase 1 COBIT projects
      • Documentation
      • Implement Phase 1 projects
      • Assess
      • Iterate
    36. Security Baseline Projects
      • Plan and Organize
      • Step 1 - Define the Information Architecture
        • Security requirements
        • Projects:
          • HIPAA Security Standard implementation
          • ZOCA II
    37. Security Baseline Projects
      • Acquire and Implement
      • Step 10 – Identify Automated Solutions
        • Consider security risks of automated solutions
        • Projects:
          • Vendor Security Questionnaire
          • Risk Assessment
          • Vulnerability Assessment
    38. Security Baseline Projects
      • Monitor and Evaluate
      • Step 38 – Monitor Performance of Security Controls
        • Periodically: Assess Controls, Reassess Exceptions, Evaluate Effectiveness, Monitor Compliance
        • Projects:
          • Vulnerability Assessment
          • IPW – Information Policy Workgroup
          • SPCR – Security Policy Compliance Review
    39. Information Lifecycle Management *From http://www.cacr.math.uwaterloo.ca/conferences/2005/psw/gingras.ppt
    40. Supporting Work
      • Risk Analysis
      • Business Impact Analysis (BIA)
      • Business Continuity Plan (BCP/DRP)
      • Test Plans
      • Vulnerability Analysis
      • Incident Response Plan
    41. Discussion?

    + Barry CaplinBarry Caplin, 8 months ago

    custom

    1179 views, 0 favs, 0 embeds more stats

    Use of the COBIT Security Baseline as a framework f more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 1179
      • 1179 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 99
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories