Ict Compliance @ Gartner (August 2005)

1,620 views

Published on

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,620
On SlideShare
0
From Embeds
0
Number of Embeds
162
Actions
Shares
0
Downloads
25
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Ict Compliance @ Gartner (August 2005)

    1. 1. Information Technology Attorneys Snapshot of Current State of ICT Regulatory Compliance in South Africa Lance Michalson Gartner Symposium ITXPO 2005 01 August 2005 Cape Town, South Africa
    2. 2. Current Legal Compliance Landscape
    3. 3. Compliance v Best Practice v Risk Management Compliance Best Practice Risk Management Technology Risk Tech Legal Risk Wide Narrow
    4. 4. Example Compliance issues Issue Offence Crypto supplier not registered with DOC Offence (fine or imprisonment not exceeding 2 years) No corporate info on e-mail Offence ito Companies Act s50.1.c arw s50.4, s171.1 arw s441.1.m, s50.1.c arw s441.1.k No express or implied consent to monitoring paper and electronic communications Fine not exceeding R2m or imprisonment not exceeding 10 years | Inadmissible evidence
    5. 5. Example Tech Legal Risk Issues Issue Risk No software development agreement in place Company does not own the software Various factors might influence the admissibility and evidential weight of electronic documents Inadmissibility of evidence. Compromised chances of success of litigation (resulting possible reputational damage, monetary loss – damages, legal costs etc.) No e-mail footer (signature / disclaimer) Vicarious liability (e.g. for defamation)
    6. 7. Legislative Process LEGISLATURE <ul><li>Parliament </li></ul><ul><li>Makes new laws </li></ul><ul><li>Amend existing laws </li></ul><ul><li>Repeal old laws </li></ul><ul><li>Provincial Legislatures </li></ul><ul><li>Municipal Councils </li></ul>EXECUTIVE JUDICIARY CONSTITUTION
    7. 8. South African ICT Regulatory Hype Cycle Visibility Trough of Disillusionment Slope of Enlightenment Plateau of Productivity Business Trigger Maturity Peak of Inflated Expectations
    8. 9. Process followed <ul><li>What was included </li></ul><ul><ul><li>Primary ICT laws in SA </li></ul></ul><ul><ul><li>NB SA adopted Standards </li></ul></ul><ul><ul><li>NB foreign laws impacting some SA Companies </li></ul></ul><ul><li>What was excluded </li></ul><ul><ul><li>Secondary laws affected by primary laws (e.g. record retention laws) </li></ul></ul>
    9. 10. South African ICT Regulatory Hype Cycle Compliance requirements develop at different rates Visibility Trough of Disillusionment Slope of Enlightenment Plateau of Productivity Business Trigger Peak of Inflated Expectations Maturity Acronym Key ASPs = Authentication Service Providers RIC = Regulation of Interception of Communications etc. Act 70 of 2002 Less than two years Two years to five years Five years to 10 years Key: Time to Plateau Infosec / SANS 17799 ECT Act (2002) Basel II (1999) RM / SANS 15489 PROATIA (2000) Sarbanes-Oxley Act (2002) RIC (monitoring) Data Privacy SANS 15801 Critical Databases, Crypto Providers and ASPs Convergence Bill (2005) King II (2002) EU Data privacy Directive FICA
    10. 11. Life Cycle of an Act of Parliament Issue Paper Discussion Paper Green Paper White Paper or Fast Track to Bill Bill Parliamentary Portfolio Committee Hearings Act before National Council of Provinces Act before National Assembly Signed by President & Gazetted Regulations, Notices DRAFTING PERIOD INFLUENCE PERIOD PREPARE TO COMPLY IP PC Cabinet Source : Department of Justice and Constitutional Development http://www.doj.gov.za/2004dojsite/legislation/legprocess.htm Last updated: 01 August 2005
    11. 12. Where Key Pieces of Legislation Fit in Issue Paper Discussion Paper Green Paper White Paper or Fast Track to Bill Bill Parliamentary Portfolio Committee Hearings Act before National Council of Provinces Act before National Assembly Signed by President + Gazetted Regulations, Notices IP PC Data Privacy Convergence Bill RIC (not yet promulgated) ECT Act Critical Database Regs ECT Act Crypto, ASP, Domain Name Regs Regs not published for comment Regs published for comment, not yet promulgated Key: Status of Regulations PC IP DRAFTING PERIOD INFLUENCE PERIOD PREPARE TO COMPLY Last updated: 01 August 2005 Cabinet
    12. 13. Optimum points of engagement June 2005 August 2005 December 2005 Convergence Bill Data Privacy Discussion Paper / Green Paper Critical Database Regulations comments & Crypto Provider enactment (ECT Act) January 2006 Possible Gazetting of Monitoring Act (anytime)
    13. 14. What can be done now? <ul><li>Critical Databases </li></ul><ul><li>Data Privacy </li></ul><ul><li>Monitoring </li></ul><ul><li>King II </li></ul><ul><ul><li>Information Security Best Practice Guide for South African Directors </li></ul></ul>
    14. 17. Chapter lX: Protection of Critical Databases Chapter lX: Protection of Critical Databases Scope of Critical Database Protection S57 S56 S55 S54 S53 S58 Identification of critical data and databases Registration Of Critical Databases Management Of Critical Databases Restrictions On disclosure of Information Right of Inspection Non Compliance with Chapter S52 Chapter lX: Protection of Critical Databases Aim is to facilitate the identification and registration of critical databases within the Republic. Critical databases are defined as databases that contain information that if compromised could threaten the security of the Republic or the economic and social well being of it’s citizens. The Act stipulates criteria for the identification, registration and management of critical databases as well as controls to ensure that the integrity and confidentiality of data relating to and contained in these databases is maintained such as the right to audit and restrictions and penalties resulting in unauthorised or illegal disclosure of information contained in or about these databases. In November 2003 the Minister of Communications awarded a tender to a consortium of Consultants to undertake an inventory of all major databases in South Africa.
    15. 18. Management of Critical Databases <ul><li>Management of critical databases </li></ul><ul><li>The Minister may prescribe minimum standards or prohibitions in respect of- </li></ul><ul><li>the general management of critical databases; </li></ul><ul><li>access to, transfer and control of critical databases; </li></ul><ul><li>infrastructural or procedural rules and requirements for securing the integrity and authenticity of critical data; </li></ul><ul><li>procedures and technological methods to be used in the storage or archiving of critical databases ; </li></ul><ul><li>disaster recovery plans in the event of loss of critical databases or parts thereof; and </li></ul><ul><li>any other matter required for the adequate protection, management and control of critical databases. </li></ul>
    16. 19. Privacy
    17. 20. State of SA privacy regulation <ul><li>Law Reform Commission Issue Paper recommends: </li></ul><ul><ul><li>privacy and data protection should be regulated by legislation ; </li></ul></ul><ul><ul><li>a statutory regulatory agency should be established; </li></ul></ul><ul><ul><li>a flexible approach should be followed in which industries will develop their own codes of practice (in accordance with the principles set out in the legislation) which will be overseen by the regulatory agency; </li></ul></ul><ul><ul><li>general principles of data protection should be developed and incorporated in the legislation. </li></ul></ul>
    18. 21. Data Protection Principles <ul><li>Limitation on collection (consent) </li></ul><ul><li>Specified purpose </li></ul><ul><li>Limitation on disclosure </li></ul><ul><li>Data quality (relevance) </li></ul><ul><li>Security safeguards </li></ul><ul><ul><li>Against unauthorised access, destruction use, modification disclosure </li></ul></ul><ul><ul><li>Role of crypto </li></ul></ul>
    19. 22. Monitoring
    20. 23. Monitoring e-communications <ul><li>1992 v 2002 (RIC) Acts </li></ul><ul><li>RIC is all about: </li></ul><ul><ul><li>Monitoring in a “legally compliant manner” </li></ul></ul><ul><ul><li>Putting the correct processes and procedures in place </li></ul></ul>
    21. 24. Monitoring <ul><li>Section 7 “business exception” </li></ul><ul><li>System controller (SC) (CEO) </li></ul><ul><li>4 requirements: </li></ul><ul><ul><li>Express / implied consent of SC </li></ul></ul><ul><ul><li>Particular purpose </li></ul></ul><ul><ul><li>E-communications tools owned by business </li></ul></ul><ul><ul><li>Reasonable efforts by SC to give advanced notice OR express / implied consent of person being monitored </li></ul></ul><ul><li>R2m or 10 years </li></ul>
    22. 25. Some Monitoring Issues <ul><li>What constitutes written consent? </li></ul><ul><li>What constitutes implied consent? </li></ul><ul><li>Is per interception consent necessary? </li></ul><ul><li>Will a blanket consent suffice? </li></ul><ul><li>How does the CEO demonstrate “reasonable efforts” </li></ul><ul><li>How does one protect the CEO? </li></ul>
    23. 26. Monitoring Matrix Implied consent and reasonable efforts demonstrated by Written consent demonstrated by CEO is protected by Monitoring Policy Acceptance of Monitoring Policy CEO Delegation to IT department FAQ Pro-Forma Interception Request Glossary of Terms Pro-Forma Interception Report to the Board Log-on Notice Log-on Notice Monitoring Policy Notice to Users Reminder e-mail from IT department
    24. 28. Compliance & Risk Cocktail ACTS OF PARLIAMENT ECT ACT PROATIA, 2002 Monitoring Act COMMON LAW BEST PRACTICE INFORMATION RISK MANAGEMENT Contract Delict (Negligence – duty to take reasonable steps) SANS 17799 MISS (Govt depts) COSO ERM COBIT SEE OUR INFORMATION & TECHNOLOGY COMPLIANCE AND LEGAL RISK MATRIX KING II GOOD GOVERNANCE Compliance crosses several disciplines from HR to IT to Legal to risk management Compliance is a combination of policy, process, and technology
    25. 29. THANK YOU FOR YOUR TIME!! Lance Michalson [email_address] “ IT Law with Insight” www.michalsons.com Copyright © Michalsons 2002-2009 The information contained in this presentation is subject to change without notice. Michalsons makes no warranty of any kind with regard to the material, including, but not limited to, the implied warranties of fitness for a particular purpose. Michalsons shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material. This document contains proprietary information that is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated to another language without the prior written consent of Michalsons This document is an unpublished work protected by the copyright laws and is proprietary to Michalsons. Disclosure, copying, reproduction, merger, translation, modification, enhancement, or use by any unauthorised person without the prior written consent of Michalsons is prohibited. Contact Lance Michalson at lance@michalsons.com for permission to copy.

    ×