ISM3 v2.3 Maturity & Metrics

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

    Notes on slide 1

    Goals, Objectives, Targets, Quality, Security

    There are three types

    Limitations or Boundaries?

    Success, e.g: Tell the time.

    Quality, e.g: Tell the time accurately.

    Security, e.g: Tell the time for the next one thousand years.

    There are three types of Obligations: Success: Comply with Personal Data Protection Laws Quality: According to the spirit of the law, not the letter. Security: Without exceptions. Limitations or Boundaries?

    Limitations or Boundaries?

    Limitations or Boundaries?

    Limitations or Boundaries?

    Limitations or Boundaries?

    There are three types of Obligations: Success: Comply with Personal Data Protection Laws Quality: According to the spirit of the law, not the letter. Security: Without exceptions. Limitations or Boundaries?

    Professional and otherwise

    Security Targets measure the achievement of security objectives in business terms.

    This information is an important resource for selection of security measures and optimizing the security investment. This information is an important resource for the security norms framework, where these expectations are turned into specific requirements.

    This information is an important resource for selection of security measures and optimising the security investment. This information is an important resource for the security norms framework, where these expectations are turned into specific requirements.

    Take the worry out and think about the results, get

    Goals, Objectives, Targets, Quality, Security

    Different accreditable maturity levels can be adequate for organizations with different resources. A maturity level can be used as a way to show progress and a step to achieving higher levels. Early investment in security brings the highest return. A binary compliant / not compliant approach can discourage initial invesment.

    Favorites, Groups & Events

    ISM3 v2.3 Maturity & Metrics - Presentation Transcript

    1. Metrics & Maturity Cartagena, 5 de Agosto de 2009 © ISM3 Consortium 2009
    2. Goals, Objectives, Thresholds, Processes, Value, Management, Metrics, Maturity
    3. Goals
    4. The motivation is to achieve broad needs, wanted p ositive outcomes , e.g: meeting commitments.
    5.  
    6.  
    7. Goal: Success
    8. Goal: Quality
    9. Goal: Security
    10. Obligations
    11. The motivation is to prevent unwanted negative outcomes, e.g: breach of contract.
    12. Goals & Obligations Business Goals Obligations Success What we want to What we have to Quality As well as we want to As well as we have to Security As reliably as we want to As reliably as we have to
    13. Success: Achieve Mission Quality: Achieve Vision Security: Existence
    14. Success: Have Reputation Quality: Grow Reputation Security: Maintain Reputation
    15. Success: Have Brand Quality: Grow Brand Security: Maintain Brand
    16. Success: Have Revenue Quality: Grow Revenue Security: Maintain Revenue
    17. Success: Get Talent Quality: Foster Talent Security: Retain Talent
    18.  
    19. Success: Comply with Social Responsibilities
    20. Success: Comply with Regulations
    21. Success: Comply with Contracts
    22. Success: Comply with Ethics
    23. Technical Technical Obligations Success: S ystems are as free of weaknesses as possible, Systems are visible to trusted systems only, Systems that need to be visible to not trusted systems are the least visible possible, Systems run trusted services only, The electricity, temperature and humidity where systems operate exceeds the systems needs.
    24.  
      • Objectives: Specific things that have to happen for Goals and Obligations to be met
    25. Targets: A threshold for an Objective to be considered successful.
    26. Sample Objectives
      • Paying the payroll on the 1st of every month;
      • Paying all incoming invoices within a certain time frame;
      • Paying taxes in time;
      • Invoicing all products and services provided;
      • Delivering the products and services when and where committed by the organization;
      • Keeping all necessary records to pass any audit successfully (i.e., tax audit, software license audit, etc.)
    27. Payroll Objectives Payroll Contribute to Goals Contribute to Obligations Success Reward your work Because we have a contract Quality Broken down so you understand each item With the minimum fields mandated Security No excuses not to We will get fined if we regularly fail
    28. Payroll Thresholds Payroll Goals Obligations Success No later than the 2 nd commercial day of the month No later than the latest date permitted by labour law Quality Understood by 95% of freshly recruited employees without help Get reported less than once a year Security Successful 97% of the months in ten years Get fined less than once every five years
    29. Sample Information Security Objectives
      • Goals -> “Secrets should be accessible to authorized users only”
      • Obligations -> “Repositories with Personal information have to be registered with the Data Protection agency”
      • Technical Obligations -> “Systems are as free of weaknesses as possible”
      • Deal with goals, coordination and provision of resources;
      • Deal with the design and implementation of the ISM system, objectives and management of resources;
      • Deal with achieving defined objectives by means of technical processes.
      Management Levels Strategic Practices Tactical Practices Operational Practices
    30. Generic Goals
      • Prevent and mitigate incidents that could jeopardize the organization’s property and the output of products and services that rely on information systems;
      • Optimise the use of information, money, people, time and infrastructure.
    31. Strategic Goals
      • Provides leadership and coordination of:
        • Information security;
        • Physical security;
        • Workplace security (outside scope of ISM3);
        • Interaction with organizational units;
      • Reviews and improves the information security management system;
      • Provides resources for information security;
      • Defines relationships with other organisations;
      • Defines Security Objectives consistent with organizational goals and obligations, protecting stakeholders interests;
      • Sets the organizational scheme of delegation.
    32. Tactical Goals
      • Provide feedback to Strategic Management;
      • Define the environment for Operational Management.
      • Define Security Targets;
      • Select appropriate processes to achieve the Security Targets;
      • Manage budget, people and other resources allocated to information security
    33. Operational Goals
      • Provide feedback to Tactical Management;
      • Identify and protect assets;
      • Protection and support of information systems throughout their lifecycle;
      • Management of the security measures lifecycle;
      • Apply allocated resources efficiently and effectively;
      • Carry out processes for incident prevention, detection and mitigation (both real time and following an incident).
    34. Process Template
    35. Process
      • Description: The activity performed in the process.
      • Documentation: Policies, Procedures and Templates Process Definitions needed to describe and perform the process.
      • Process Owner: Every process should have one and no more than one process owner.
    36. Process
      • Inputs: Inputs to the process. (Inputs in italics or obtained from sources other than documents)
      • Work Products: Results of the process. (Work Products in italics are work products other than documents)
      • Value: How the process contributes to specific and generic goals.
    37. Value
      • Managing is achieving goals with the resources available for it.
      • There are specific activities for management that we will call “Management Practices”.
      Management
      • Testing: Assessment of whether process outputs are as expected when test data is put in.
      Mana gement Practices
      • Monitoring: Checking whether the outputs of the process and the resources used are within normal range.
      Management Practices
      • Improving: Making changes in the process to make it more suitable for the purpose, or to reduce usage of resources.
      Management Practices
      • Planning. Organizing and forecasting the amount, assignment and milestones of tasks, resources, budget, deliverables and performance of a process.
      Management Practices
      • Assessment. How well the process matches the organization's needs and compliance goals.
      Management Practices
      • Audit. Whether the process inputs, activities and results match their documentation.
      Management Practices
      • Certify: Whether the process inputs, process documentation, activities and results comply with a pre-defined standard, law or regulation.
      Management Practices
      • Benefits realization: Show how achieving security objectives contributes to achieving business objectives.
      Management Practices
      • The more sophisticated your management practices, the higher your capability.
      Management and Capability
      • It is possible to assess the capability of a process checking the metrics used to manage it.
      Management
      • You can perform few management practices without metrics.
    38. Metrics
      • A quantitative measurement that can be interpreted in the context of a series of previous or equivalent measurements
    39. Ty pes of Process Metrics
      • Activity: Number of outputs produced and their mean age.
    40. Types of Process Metrics
      • Scope: Percentage of all inputs producers covered by this process.
    41. Types of Process Metrics
      • Unavailability: Number, frequency and duration of interruptions in the normal operation of the process.
    42. Types of Process Metrics
      • Effectiveness: Number, mean time between inputs and percentage of Inputs that produce an Output.
    43. Types of Process Metrics
      • Efficiency: Ratio between the number of outputs submitted and the available resources for this process in actual use.
    44. Types of Process Metrics
      • Load: Percentage of resources reserved for the process in actual use.
    45. Types of Process Metrics
      • Quality: Measure of the fitness for purpose of the outputs.
        • Description of what is measured
        • How is the metric measured
        • How often is the measurement taken
        • How are the thresholds calculated
        • Current range of values considered normal for the metric
        • Best possible value of the metric
        • Units of measurement
      Metrics Specification
    46. Sample: Optimizing
      • Cobit: “Good Practices are followed and automated”
      • CMMI: “An optimizing process is a quantitatively managed process that is improved based on an understanding of the common causes of variation inherent in the process. The focus of an optimizing process is on continually improving the range of process performance through both incremental and innovative improvements”
    47. 3 – Definición Objetiva de Madurez
    48. Value
    49. Goals
    50. THANK YOU
    51. ISM3 Maturity Levels (examples)
      • ISM3 Basic Level - Significant risk reduction from technical threats, for a minimum investment in essential ISM processes.
        • For organizations with low Information Security Targets in low risk environments.
      • ISM3 SMEs Level - Highest risk reduction from technical threats, for a significant investment in Information Security processes.
        • For organizations with high Information Security Targets in normal or high-risk environments.
      • ISM3 Military Level - Highest risk reduction from technical and internal threats, for a high and optimized investment in Information Security processes.
        • For organizations affected by specific requirements (such as utilities, and financial institutions) with high Information Security Targets in normal or high-risk environments.
    52. ISM3 Capability Levels Capability Level Metrics Requirements Enabled Managed Practices Basic Documentation Audit and Certify. Defined Basic, plus Activity, Scope, Unavailability and Effectiveness Basic, plus Test Managed Defined, plus Load Defined, plus Monitor, Benefits Realization, Planning and removing weaknesses before they produce incidents, and getting feedback on the result of changes. Controlled Managed, plus Quality Managed, plus Assessment and removing bottlenecks that hamper performance. Optimized Controlled, plus Efficiency Controlled, plus finding points of diminishing return and making trade-offs.
    53. Use case – Malware Management
      • Use case – ISM3-less management
        • Motivation: Clean viruses or your business will sink.
        • Objective: No system should get a virus ever
        • Activity: Install antivirus on personal computers, servers, mail servers, add antivirus functionality to firewalls, add antispyware, antitrojan, antirookit to the mix.
        • Policy: Prevent any USB, DVD, to touch any company system without being searched for viruses.
        • Success criterion: When no system gets ever a virus.
        • Continuous improvement: Add more antimalware controls (Tripwire, CORE, etc)
      • Use Case – ISM3-style management
        • Motivation: Unfortunately systems, specially Windows and malware prone. We should invest proportionally to the damage they can make.
        • Goal: Systems should accomplish their business role with or without malware.
        • Activity: Install antimalware in vulnerable systems. Measure activity, scope, update and availability of antimalware. Consider other measures, like using less malware prone systems.
        • Policy: Use in every system the antimalware protection that will detect malware and prevent the system from failing to play its business role.
        • Success criterion: When protected system play their business role without interruption or degradation.
        • Continuous improvement: Use metrics to improve the antimalware protection and use those with better effectively and ROI.
      Use case – Malware Management
    SlideShare Zeitgeist 2009

    + vaceitunovaceituno Nominate

    custom

    80 views, 0 favs, 0 embeds more stats

    Como relacionar los objetivos de negocio con los pr more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 80
      • 80 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 0
    • Downloads 7
    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