in

Mapping Regulatory Requirements

Last post 08-09-2007 5:01 AM by Paolo Ottolino. 2 replies.
Page 1 of 1 (3 items)
Sort Posts: Previous Next
  • 07-12-2007 10:00 AM

    • dmarkiewicz
    • Top 10 Contributor
    • Joined on 02-28-2007
    • Pittsburgh, PA
    • Posts 30
    • Points 170

    Mapping Regulatory Requirements

    In ISMv1.0 there was a project for mapping varying federal and/or international regulations.  Is that still a project somewhere?   

    • Post Points: 40
  • 07-13-2007 4:02 AM In reply to

    • mcurphey
    • Top 10 Contributor
    • Joined on 02-13-2007
    • Europe
    • Posts 199
    • Points 2,130

    Re: Mapping Regulatory Requirements

    Hi Doug 

    We talked about doing it but rationalized somewhat when we saw how long it was taking us all to get things underway. There are various people working on various other projects. Don't need permission or anything drackonian, just do it and publish it here and away we go. For the policy and regulations mapping I think the idea was to build something more than a spreadheet ie a web app to show it but then again if it was in a spreadsheet I am sure someone could easily use asp.net to build a searchable, sortable web app from the data source very easily.

    • Post Points: 40
  • 08-09-2007 5:01 AM In reply to

    Re: Mapping Regulatory Requirements

    Hi, 

    The compliance must be addressed on more level of abstraction, depending on the company roles that have to analyze the compliance results.
    It must be clear the goal, for each function in the company. Tipically the roles involved are:
    - CxO
    - Security Management
    - Operations

    The following elements must be addressed in the Compliance Program:
    a) the definition of processes regarding compliance activities

    Enterprise Compliance Program Figure


    b) the actual mapping to and from
      . Regulation (Privacy, SOX, PCI, etc)
      . Internal Policy (Information Security Policy, regulation specific, etc)
      . Baseline (SOX for Windows, PCI for Unix, etc)
      . Control Set (actual control to be configured on the enterprise compliance tool)

     

    Compliance System Taxonomy Figure


    c) the Remediation (in terms of strategy and practical tasks)
    d) the Reporting (one of the most important tasks), to be performed at each of the 3 level:
      . Policy Compliance (for CxO, generally) in order to assess the overall actual level of compliance to the specific regulation
      . Baseline (for Security Management) in order to describe some more details, showing the  effectiveness of the security infrasctructure in place
      . Control Sets (for Operations) in order to show the specific level of effectiveness of each practical control

    I work for a famous vendor.
    We have some products about compliance and we use to develop some add-ons (taylored to the customer specific requests) in order to accomplish b) and d)

    Obviously, there must  a methodology for addressing compliance, not based on the products. It must be based on the elements I wrote before
    The goodness of the tool stands in the capabilities of help in the implementation of the compliance program



    Paolo Ottolino

    CCSE OPST CISSP-ISSAP CISA CISM
    -----------------------------------------------------------
    ICT Senior Security Advisor

    paolo.ottolino@gmail.com
    http://www.8linux.org
    Filed under:
    • Post Points: 25
Page 1 of 1 (3 items)
All Rights Reserved - The ISM-Community
Powered by Community Server (Commercial Edition), by Telligent Systems