Monetary Authority of Singapore TECHNOLOGY RISK MANAGEMENT GUIDELINES

Size: px
Start display at page:

Download "Monetary Authority of Singapore TECHNOLOGY RISK MANAGEMENT GUIDELINES"

Transcription

1 Monetary Authority of Singapore TECHNOLOGY RISK MANAGEMENT GUIDELINES JUNE 2013

2 TABLE OF CONTENTS 1 INTRODUCTION APPLICABILITY OF THE GUIDELINES OVERSIGHT OF TECHNOLOGY RISKS BY BOARD OF DIRECTORS AND SENIOR MANAGEMENT Roles and Responsibilities IT Policies, Standards and Procedures People Selection Process IT Security Awareness TECHNOLOGY RISK MANAGEMENT FRAMEWORK Information System Assets Risk Identification Risk Assessment Risk Treatment Risk Monitoring and Reporting MANAGEMENT OF IT OUTSOURCING RISKS Due Diligence Cloud Computing ACQUISITION AND DEVELOPMENT OF INFORMATION SYSTEMS IT Project Management Security Requirements and Testing Source Code Review End User Development IT SERVICE MANAGEMENT Change Management Program Migration Incident Management Problem Management Capacity Management SYSTEMS RELIABILITY, AVAILABILITY AND RECOVERABILITY Systems Availability Disaster Recovery Plan Disaster Recovery Testing

3 8.4 Data Backup Management OPERATIONAL INFRASTRUCTURE SECURITY MANAGEMENT Data Loss Prevention Technology Refresh Management Networks and Security Configuration Management Vulnerability Assessment and Penetration Testing Patch Management Security Monitoring DATA CENTRES PROTECTION AND CONTROLS Threat and Vulnerability Risk Assessment Physical Security Data Centre Resiliency ACCESS CONTROL User Access Management Privileged Access Management ONLINE FINANCIAL SERVICES Online Systems Security Mobile Online Services and Payments Security PAYMENT CARD SECURITY (AUTOMATED TELLER MACHINES, CREDIT AND DEBIT CARDS) Payment Card Fraud ATMs and Payment Kiosks Security IT AUDIT Audit Planning and Remediation Tracking...43 APPENDIX A: SYSTEMS SECURITY TESTING AND SOURCE CODE REVIEW...44 APPENDIX B: STORAGE SYSTEM RESILIENCY...47 APPENDIX C: CRYPTOGRAPHY...49 APPENDIX D: DISTRIBUTED DENIAL-OF-SERVICE PROTECTION...51 APPENDIX E: SECURITY MEASURES FOR ONLINE SYSTEMS...53 APPENDIX F: CUSTOMER PROTECTION AND EDUCATION

4 1 INTRODUCTION The advancement of information technology ( IT ) has brought about rapid changes to the way businesses and operations are being conducted in the financial industry. IT is no longer a support function within a financial institution 1 ( FI ) but a key enabler for business strategies including reaching out to and meeting customer needs Financial systems and networks supporting FIs business operations have also grown in scope and complexity over the years. FIs offering a diversity of products and services could have their financial systems operating in multiple locations and supported by different service providers FIs are also faced with the challenge of keeping pace with the needs and preferences of consumers who are getting more IT-savvy and switching to internet and mobile devices for financial services, given their speed, convenience and ease of use. Increasingly, FIs are deploying more advanced technology and online systems, including internet banking systems, mobile banking and payment systems, online trading platforms and insurance portals, to reach their customers. In this regard, FIs should fully understand the magnitude and intensification of technology risks from these systems. They should also put in place adequate and robust risk management systems as well as operating processes to manage these risks The Technology Risk Management Guidelines (the Guidelines ) set out risk management principles and best practice standards to guide the FIs in the following: a. Establishing a sound and robust technology risk management framework; b. Strengthening system security, reliability, resiliency, and recoverability; and c. Deploying strong authentication to protect customer data, transactions and systems While the Guidelines are not legally binding, the degree of observance with the spirit of the Guidelines by an FI is an area of consideration in the risk assessment of the FI by MAS. 1 Financial institution has the same meaning as in section 27A(6) of the Monetary Authority of Singapore Act (Cap. 186). 4

5 2 APPLICABILITY OF THE GUIDELINES The Guidelines are statements of industry best practices which FIs are expected to adopt. The Guidelines do not affect, and should not be regarded as a statement of the standard of care owed by FIs to their customers. Where appropriate, FIs may adapt these guidelines, taking into account the diverse activities they engage in and the markets in which they conduct transactions. FIs should read the Guidelines in conjunction with relevant regulatory requirements and industry standards The objective of the Guidelines is to promote the adoption of sound practices and processes for managing technology. 5

6 3 OVERSIGHT OF TECHNOLOGY RISKS BY BOARD OF DIRECTORS AND SENIOR MANAGEMENT IT is a core function of many FIs. When critical systems fail and customers cannot access their accounts, an FI s business operations may immediately come to a standstill. The impact on customers would be instantaneous, with significant consequences to the FI, including reputational damage, regulatory breaches, revenue and business losses In view of the importance of the IT function in supporting an FI s business, the board of directors and senior management should have oversight of technology risks and ensure that the organisation s IT function is capable of supporting its business strategies and objectives. 3.1 Roles and Responsibilities The board of directors and senior management should ensure that a sound and robust technology risk management framework is established and maintained. They should also be involved in key IT decisions They should also be fully responsible for ensuring that effective internal controls and risk management practices are implemented to achieve security, reliability, resiliency and recoverability The board of directors and senior management should give due consideration to cost-benefit issues, including factors such as reputation, customer confidence, consequential impact and legal implications, with regard to investment in controls and security measures for computer systems, networks, data centres ( DC ), operations and backup facilities. 3.2 IT Policies, Standards and Procedures FIs should establish IT policies, standards and procedures, which are critical components of the framework, to manage technology risks and safeguard information system assets 2 in the organisation Due to rapid changes in the IT operating and security environment, policies, standards and procedures should be regularly reviewed and updated. 2 Information systems assets refer to data, systems, network devices and other IT equipment. 6

7 3.2.3 Compliance processes should be implemented to verify that IT security standards and procedures are enforced. Follow-up processes should be implemented so that compliance deviations are addressed and remedied on a timely basis. 3.3 People Selection Process Careful selection of staff, vendors and contractors is crucial to minimise technology risks due to system failure, internal sabotage or fraud. As people play an important role in managing systems and processes in an IT environment, the FI should implement a screening process that is comprehensive and effective Staff, vendors and contractors, who are authorised to access the FI s systems, should be required to protect sensitive or confidential information. 3.4 IT Security Awareness A comprehensive IT security awareness training program should be established to enhance the overall IT security awareness level in the organisation. The training program should include information on IT security policies and standards as well as individual responsibility in respect of IT security and measures that should be taken to safeguard information system assets. Every staff in the organisation should be made aware of the applicable laws, regulations, and guidelines pertaining to the usage, deployment and access to IT resources The training program should be conducted and updated at least annually and extended to all new and existing staff, contractors and vendors who have access to the FI s IT resources and systems The training program should be endorsed by senior management. It should be reviewed and updated to ensure that the contents of the program remain current and relevant. The review should also take into consideration the evolving nature of technology as well as emerging risks. 7

8 4 TECHNOLOGY RISK MANAGEMENT FRAMEWORK A technology risk management framework should be established to manage technology risks in a systematic and consistent manner. The framework should encompass the following attributes: a. Roles and responsibilities in managing technology risks; b. Identification and prioritisation of information system assets; c. Identification and assessment of impact and likelihood of current and emerging threats, risks and vulnerabilities; d. Implementation of appropriate practices and controls to mitigate risks; and e. Periodic update and monitoring of risk assessment to include changes in systems, environmental or operating conditions that would affect risk analysis Effective risk management practices and internal controls should be instituted to achieve data confidentiality 3, system security, reliability, resiliency and recoverability in the organisation. 4.1 Information System Assets Information system assets should be adequately protected from unauthorised access, misuse or fraudulent modification, insertion, deletion, substitution, suppression or disclosure The FI should establish a clear policy on information system asset protection. Criticality of information system assets should be identified and ascertained in order to develop appropriate plans to protect them. 4.2 Risk Identification Risk identification entails the determination of the threats and vulnerabilities to the FI s IT environment which comprises the internal and external networks, hardware, software, applications, systems interfaces, operations and human elements. 3 Data confidentiality refers to the protection of sensitive or confidential information such as customer data from unauthorised access, disclosure, etc. 8

9 4.2.2 A threat may take the form of any condition, circumstance, incident or person with the potential to cause harm by exploiting vulnerability in a system. The source of the threat can be natural, human or environmental. Humans are significant sources of threats through deliberate acts or omissions which could inflict extensive harm to the organisation and its information systems Security threats such as those manifested in denial of service attacks, internal sabotage and malware infestation could cause severe harm and disruption to the operations of an FI with consequential losses for all parties affected. The FI should be vigilant in monitoring such mutating and growing risks as it is a crucial step in the risk containment exercise. 4.3 Risk Assessment Following risk identification, the FI should perform an analysis and quantification of the potential impact and consequences of these risks on the overall business and operations The extent of risk impact depends on the likelihood of various threat and vulnerability pairings or linkages capable of causing harm to the organisation should an adverse event occur The FI should develop a threat and vulnerability matrix to assess the impact of the threat to its IT environment. The matrix will also assist the FI in prioritising IT risks. 4.4 Risk Treatment For each type of risk identified, the FI should develop and implement risk mitigation and control strategies that are consistent with the value of the information system assets and the level of risk tolerance Risk mitigation entails a methodical approach for evaluating, prioritising and implementing appropriate risk-reduction controls. A combination of technical, procedural, operational and functional controls would provide a rigorous mode of reducing risks As it may not be practical to address all known risks simultaneously or in the same timeframe, the FI should give priority to threat and vulnerability pairings with high risk ranking which could cause significant harm or impact to the FI s operations. The FI should assess its risk tolerance for damages and losses in 9

10 the event that a given risk-related event materialises. The costs of risk controls should be balanced against the benefits to be derived It is imperative that the FI is able to manage and control risks in a manner that will maintain its financial and operational viability and stability. When deciding on the adoption of alternative controls and security measures, the FI should also be conscious of costs and effectiveness of the controls with regard to the risks being mitigated The FI should refrain from implementing and running a system where the threats to the safety and soundness of the IT system are insurmountable and the risks cannot be adequately controlled As a risk mitigating measure, the FI could consider taking insurance cover for various insurable risks, including recovery and restitution costs. 4.5 Risk Monitoring and Reporting The FI should maintain a risk register which facilitates the monitoring and reporting of risks. Risks of the highest severity should be accorded top priority and monitored closely with regular reporting on the actions that have been taken to mitigate them. The FI should update the risk register periodically, and institute a monitoring and review process for continuous assessment and treatment of risks To facilitate risk reporting to management, the FI should develop IT risk metrics to highlight systems, processes or infrastructure that have the highest risk exposure. An overall technology risk profile of the organisation should also be provided to the board of directors and senior management. In determining the IT risk metrics, the FI should consider risk events, regulatory requirements and audit observations Risk parameters may shift as the IT environment and delivery channels change. Thus, the FI should review and update the risk processes accordingly, and conduct a re-evaluation of past risk-control methods with renewed testing and assessment of the adequacy and effectiveness of risk management processes Management of the IT function should review and update its IT risk control and mitigation approach, taking into account changing circumstances and variations in the FI s risk profile. 10

11 5 MANAGEMENT OF IT OUTSOURCING RISKS IT outsourcing comes in many forms and permutations. Some of the most common types of IT outsourcing are in systems development and maintenance, support to DC operations, network administration, disaster recovery services, application hosting, and cloud computing. Outsourcing can involve the provision of IT capabilities and facilities by a single third party or multiple vendors located in Singapore or abroad. 5.1 Due Diligence The board of directors and senior management should fully understand risks associated with IT outsourcing. Before a service provider is appointed, due diligence should be carried out to determine its viability, capability, reliability, track record and financial position The FI should ensure that contractual terms and conditions governing the roles, relationships, obligations and responsibilities of all contracting parties are set out fully in written agreements. The requirements and conditions covered in the agreements would usually include performance targets, service levels, availability, reliability, scalability, compliance, audit, security, contingency planning, disaster recovery capability and backup processing facility The FI should ensure that the service provider grants access to all parties nominated by the FI to its systems, operations, documentation and facilities in order to carry out any review or assessment for regulatory, audit or compliance purposes. In addition, the engagement of the service provider should not hinder the ability of the regulatory authorities to assess the FI s IT risks which would include inspecting, supervising or examining the service provider s roles, responsibilities, obligations, functions, systems and facilities. In this regard, the FI should ensure that the contractual agreements with the service provider recognise the authority of regulators to perform an assessment on the service provider IT outsourcing should not result in any weakening or degradation of the FI s internal controls. The FI should require the service provider to employ a high standard of care and diligence in its security policies, procedures and controls to protect the confidentiality and security of its sensitive or confidential information, such as customer data, computer files, records, object programs and source codes. 11

12 5.1.5 The FI should require the service provider to implement security policies, procedures and controls that are at least as stringent as it would expect for its own operations The FI should monitor and review the security policies, procedures and controls of the service provider on a regular basis, including commissioning or obtaining periodic expert reports on security adequacy and compliance in respect of the operations and services provided by the service provider The FI should require the service provider to develop and establish a disaster recovery contingency framework which defines its roles and responsibilities for documenting, maintaining and testing its contingency plans and recovery procedures All parties concerned, including those from the service provider, should receive regular training in activating the contingency plan and executing recovery procedures The disaster recovery plan should be reviewed, updated and tested regularly in accordance with changing technology conditions and operational requirements The FI should also put in place a contingency plan based on credible worstcase scenarios for service disruptions to prepare for the possibility that its current service provider may not be able to continue operations or render the services required. The plan should incorporate identification of viable alternatives for resuming its IT operations elsewhere. 5.2 Cloud Computing Cloud computing is a service and delivery model for enabling on-demand network access to a shared pool of configurable computing resources (servers, storage and services). Users of such services may not know the exact locations of servers, applications and data within the service provider s computing infrastructure for the hosting, storing or processing of information In performing its due diligence for all forms of outsourcing arrangements, the FI should be aware of cloud computing s unique attributes and risks especially in areas of data integrity, sovereignty, commingling, platform multi-tenancy, recoverability and confidentiality, regulatory compliance, auditing and data offshoring. 12

13 5.2.3 As cloud computing service providers may adopt multi-tenancy and data commingling architectures in order to process data for multiple customers, the FI should pay attention to these service providers abilities to isolate and clearly identify its customer data and other information system assets for protection In the event of contract termination with the service provider, either on expiry or prematurely, the FI should have the contractual power and means to promptly remove or destroy data stored at the service provider s systems and backups The FI should verify the service provider s ability to recover the outsourced systems and IT services within the stipulated recovery time objective ( RTO ) prior to contracting with the service provider. 13

14 6 ACQUISITION AND DEVELOPMENT OF INFORMATION SYSTEMS Many systems fail because of poor system design and implementation, as well as inadequate testing. The FI should identify system deficiencies and defects at the system design, development and testing phases The FI should establish a steering committee, consisting of business owners, the development team and other stakeholders to provide oversight and monitoring of the progress of the project, including deliverables to be realised at each phase of the project and milestones to be reached according to the project timetable. 6.1 IT Project Management In drawing up a project management framework, the FI should ensure that tasks and processes for developing or acquiring new systems include project risk assessment and classification, critical success factors for each project phase, definition of project milestones and deliverables. The FI should clearly define in the project management framework, the roles and responsibilities of staff involved in the project The FI should clearly document project plans for all IT projects. In the project plans, the FI should set out clearly the deliverables to be realised at each phase of the project as well as milestones to be reached The FI should ensure that user functional requirements, business cases, costbenefit analysis, systems design, technical specifications, test plans and service performance expectation are approved by the relevant business and IT management The FI should establish management oversight of the project to ensure that milestones are reached and deliverables are realised in a timely manner. The FI should escalate issues or problems which could not be resolved at the project committee level to senior management for attention and intervention. 6.2 Security Requirements and Testing The FI should clearly specify security requirements relating to system access control, authentication, transaction authorisation, data integrity, system activity logging, audit trail, security event tracking and exception handling in the early 14

15 phase of system development or acquisition. The FI should also perform a compliance check on the FI s security standards against the relevant statutory requirements A methodology for system testing 4 should be established. The scope of tests should cover business logic, security controls and system performance under various stress-load scenarios and recovery conditions The FI should ensure that full regression testing is performed before system rectification or enhancement is implemented. Users whose systems and operations are affected by the system changes should review and sign off on the outcome of the tests (Refer to Appendix A for details on Systems Security Testing and Source Code Review) The FI should conduct penetration testing prior to the commissioning of a new system which offers internet accessibility and open network interfaces. The FI should also perform vulnerability scanning of external and internal network components that support the new system The FI should maintain separate physical or logical environments for unit, integration, as well as system and user acceptance testing ( UAT ), and closely monitor vendor and developers access to UAT environment. 6.3 Source Code Review There are different ways of coding programs which may conceal security threats and loopholes, deliberate or unintentional. System and user acceptance tests are usually ineffective in detecting malicious codes, trojans, backdoors, logic bombs and other malware. Black-box testing is not an effective tool in identifying or detecting these security threats and weaknesses Source code review is a methodical examination of the source code of an application with the objective of finding defects that are due to coding errors, poor coding practices or malicious attempts. It is designed to identify security vulnerabilities and deficiencies, and mistakes in system design or functionality relating to areas such as control structure, security, input validation, error handling, file update, function parameter verification, before the system is implemented. 4 System testing is broadly defined to include unit, modular, integration, system and user acceptance testing. 15

16 6.3.3 The FI should ensure that there is a high degree of system and data integrity for all systems. The FI should exercise due diligence in ensuring its applications have appropriate security controls, taking into consideration the type and complexity of services these applications provide Based on the FI s risk analysis, the FI should rigorously test specific application modules and security safeguards with a combination of source code review, exception testing and compliance review to identify errant coding practices and systems vulnerabilities that could lead to security problems, violations and incidents. 6.4 End User Development There are common business application tools and software which allow business users to develop simple applications to automate their operations, perform data analysis and generate reports for the FI and customers The FI should perform an assessment to ascertain the importance of these applications to the business Recovery measures, user access and data protection controls, at the minimum, should be implemented for such applications The FI should review and test end user developed program codes, scripts and macros before they are used so as to ensure the integrity and reliability of the applications. 16

17 7 IT SERVICE MANAGEMENT A robust IT service management framework is essential for supporting IT systems, services and operations, managing changes, incidents and problems as well as ensuring the stability of the production IT environment The framework should comprise the governance structure, processes and procedures for change management, software release management, incident and problem management as well as capacity management. 7.1 Change Management The FI should establish a change management process to ensure that changes to production systems are assessed, approved, implemented and reviewed in a controlled manner The change management process should apply to changes pertaining to system and security configurations, patches for hardware devices and software updates Prior to deploying changes to the production environment, the FI should perform a risk and impact analysis of the change request in relation to existing infrastructure, network, up-stream and downstream systems. The FI should also determine if the introduced change would spawn security implications or software compatibility problems to affected systems or applications The FI should adequately test the impending change and ensure that it is accepted by users prior to the migration of the changed modules to the production system. The FI should develop and document appropriate test plans for the impending change. The FI should obtain test results with user sign-offs prior to the migration All changes to the production environment should be approved by personnel delegated with the authority to approve change requests To minimise risks associated with changes, FIs should perform backups of affected systems or applications prior to the change. The FI should establish a rollback plan to revert to a former version of the system or application if a problem is encountered during or after the deployment. The FI should establish alternative recovery options to address situations where a change does not allow the FI to revert to a prior status. 17

18 7.1.7 Audit and security logs are useful information which facilitates investigations and trouble shooting. The FI should ensure that the logging facility is enabled to record activities that are performed during the migration process. 7.2 Program Migration Program migration involves the movement of software codes and scripts from the development environment to test and production environments. Unauthorised and malicious codes which are injected during the migration process could compromise data, systems and processes in the production environment Separate physical or logical environments for systems development, testing, staging and production should be established Where controls in the non-production environment are different or less stringent from those in the production environment, the FI should perform a risk assessment and ensure that sufficient preventive and detective controls have been implemented before connecting a non-production environment to the internet Segregation of duties should be enforced so that no single individual has the ability to develop, compile and move object codes from one environment to another After a change has been successfully implemented in the production environment, the change should also be replicated and migrated to disaster recovery systems or applications for consistency. 7.3 Incident Management An IT incident occurs when there is an unexpected disruption to the standard delivery of IT services. The FI should appropriately manage such incidents to avoid a situation of mishandling that result in a prolonged disruption of IT services or further aggravation The FI should establish an incident management framework with the objective of restoring normal IT service as quickly as possible following the incident, and with minimal impact to the FI s business operations. The FI should also establish the roles and responsibilities of staff involved in the incident 18

19 management process, which includes recording, analysing, remediating and monitoring incidents It is important that incidents are accorded with the appropriate severity level. As part of incident analysis, the FI may delegate the function of determining and assigning incident severity levels to a centralised technical helpdesk function. The FI should train helpdesk staff to discern incidents of high severity level. In addition, criteria used for assessing severity levels of incidents should be established and documented The FI should establish corresponding escalation and resolution procedures where the resolution timeframe is commensurate with the severity level of the incident The predetermined escalation and response plan for security incidents 5, should be tested on a regular basis The FI should form a computer emergency response team, comprising staff within the FI with necessary technical and operational skills to handle major incidents In some situations, major incidents may further develop unfavourably into a crisis. Senior management should be kept apprised of the development of these incidents so that the decision to activate the disaster recovery plan can be made on a timely basis. FIs should inform MAS as soon as possible in the event that a critical system has failed over to its disaster recovery system. Procedures to notify MAS of these incidents should be established Being able to maintain customer confidence throughout a crisis or an emergency situation is of great importance to the reputation and soundness of the FI. FIs should include in their incident response procedures a predetermined action plan to address public relations issues The FI should keep customers informed of any major incident. The FI should also assess the effectiveness of the mode of communication, including informing the general public, where necessary As incidents may stem from numerous factors, FIs should perform a rootcause and impact analysis for major incidents which result in severe disruption 5 Examples of security incidents include virus outbreak, malware infiltration, systems hacking, account impersonation or compromise, phishing attack, internal sabotage or denial of service attacks. 19

20 of IT services. The FI should take remediation actions to prevent the recurrence of similar incidents The FI should include in its incident report an executive summary of the incident, an analysis of root cause which triggered the event, its impact as well as measures taken to address the root cause and consequences of the event The root-cause and impact analysis report should cover the following areas: a. Root Cause Analysis i. When did it happen? ii. Where did it happen? iii. Why and how did the incident happen? iv. How often had a similar incident occurred over the last 3 years? v. What lessons were learnt from this incident? b. Impact Analysis i. Extent, duration or scope of the incident including information on the systems, resources, customers that were affected; ii. Magnitude of the incident including foregone revenue, losses, costs, investments, number of customers affected, implications, consequences to reputation and confidence; and iii. Breach of regulatory requirements and conditions as a result of the incident. c. Corrective and Preventive Measures i. Immediate corrective action to be taken to address consequences of the incident. Priority should be placed on addressing customers concerns and / or compensation; ii. Measures to address the root cause of the incident; and iii. Measures to prevent similar or related incidents from occurring The FI should adequately address all incidents within corresponding resolution timeframes and monitor all incidents to their resolution. 20

TECHNOLOGY RISK MANAGEMENT GUIDELINES

TECHNOLOGY RISK MANAGEMENT GUIDELINES CONSULTATION PAPER P012-2012 JUNE 2012 TECHNOLOGY RISK MANAGEMENT GUIDELINES PREFACE The MAS Internet Banking and Technology Risk Management Guidelines have been updated to enhance financial institutions

More information

Technology Risk Management

Technology Risk Management 1 Monetary Authority of Singapore Technology Risk Guidelines & Notices New Requirements for Financial Services Industry Mark Ames Director, Seminar Program ISACA Singapore 2 MAS Supervisory Framework Impact

More information

¼ããÀ ããè¾ã ¹ãÆãä ã¼ãîãä ã ããõà ãäìããä ã½ã¾ã ºããñ à Securities and Exchange Board of India

¼ããÀ ããè¾ã ¹ãÆãä ã¼ãîãä ã ããõà ãäìããä ã½ã¾ã ºããñ à Securities and Exchange Board of India CIRCULAR CIR/MRD/DP/13/2015 July 06, 2015 To, All Stock Exchanges, Clearing Corporation and Depositories. Dear Sir / Madam, Subject: Cyber Security and Cyber Resilience framework of Stock Exchanges, Clearing

More information

Information Security Policy September 2009 Newman University IT Services. Information Security Policy

Information Security Policy September 2009 Newman University IT Services. Information Security Policy Contents 1. Statement 1.1 Introduction 1.2 Objectives 1.3 Scope and Policy Structure 1.4 Risk Assessment and Management 1.5 Responsibilities for Information Security 2. Compliance 3. HR Security 3.1 Terms

More information

INFORMATION TECHNOLOGY SECURITY STANDARDS

INFORMATION TECHNOLOGY SECURITY STANDARDS INFORMATION TECHNOLOGY SECURITY STANDARDS Version 2.0 December 2013 Table of Contents 1 OVERVIEW 3 2 SCOPE 4 3 STRUCTURE 5 4 ASSET MANAGEMENT 6 5 HUMAN RESOURCES SECURITY 7 6 PHYSICAL AND ENVIRONMENTAL

More information

Information Security Handbook

Information Security Handbook Information Security Handbook Adopted 6/4/14 Page 0 Page 1 1. Introduction... 5 1.1. Executive Summary... 5 1.2. Governance... 5 1.3. Scope and Application... 5 1.4. Biennial Review... 5 2. Definitions...

More information

GUIDELINES ON CONTROL OBJECTIVES & PROCEDURES FOR OUTSOURCED SERVICE PROVIDERS

GUIDELINES ON CONTROL OBJECTIVES & PROCEDURES FOR OUTSOURCED SERVICE PROVIDERS GUIDELINES ON CONTROL OBJECTIVES & PROCEDURES FOR OUTSOURCED SERVICE PROVIDERS 26 June 2015 Version 1.0 THE ABS GUIDELINES ON CONTROL OBJECTIVES & PROCEDURES FOR OUTSOURCED SERVICE PROVIDERS INTRODUCTION

More information

DESIGNATED CONTRACT MARKET OPERATIONAL CAPABILITY TECHNOLOGY QUESTIONNAIRE

DESIGNATED CONTRACT MARKET OPERATIONAL CAPABILITY TECHNOLOGY QUESTIONNAIRE DESIGNATED CONTRACT MARKET OPERATIONAL CAPABILITY TECHNOLOGY QUESTIONNAIRE Please provide all relevant documents responsive to the information requests listed within each area below. In addition to the

More information

1.0 INTRODUCTION...1 2.0 RISK MANAGEMENT FRAMEWORK...3

1.0 INTRODUCTION...1 2.0 RISK MANAGEMENT FRAMEWORK...3 Monetary Authority of Singapore INTERNET BANKING AND TECHNOLOGY RISK MANAGEMENT GUIDELINES VERSION 3.0 2 JUNE 2008 TABLE OF CONTENTS 1.0 INTRODUCTION...1 2.0 RISK MANAGEMENT FRAMEWORK...3 2.1 RISK MANAGEMENT

More information

ensure prompt restart of critical applications and business activities in a timely manner following an emergency or disaster

ensure prompt restart of critical applications and business activities in a timely manner following an emergency or disaster Security Standards Symantec shall maintain administrative, technical, and physical safeguards for the Symantec Network designed to (i) protect the security and integrity of the Symantec Network, and (ii)

More information

IT General Controls Domain COBIT Domain Control Objective Control Activity Test Plan Test of Controls Results

IT General Controls Domain COBIT Domain Control Objective Control Activity Test Plan Test of Controls Results Acquire or develop application systems software Controls provide reasonable assurance that application and system software is acquired or developed that effectively supports financial reporting requirements.

More information

WEST LOTHIAN COUNCIL INFORMATION SECURITY POLICY

WEST LOTHIAN COUNCIL INFORMATION SECURITY POLICY WEST LOTHIAN COUNCIL INFORMATION SECURITY POLICY DATA LABEL: PUBLIC INFORMATION SECURITY POLICY CONTENTS 1. INTRODUCTION... 3 2. MAIN OBJECTIVES... 3 3. LEGISLATION... 4 4. SCOPE... 4 5. STANDARDS... 4

More information

1.0 INTRODUCTION...1 2.0 RISK MANAGEMENT FRAMEWORK...3

1.0 INTRODUCTION...1 2.0 RISK MANAGEMENT FRAMEWORK...3 Monetary Authority of Singapore INTERNET BANKING AND TECHNOLOGY RISK MANAGEMENT GUIDELINES VERSION 3.0 2 JUNE 2008 TABLE OF CONTENTS 1.0 INTRODUCTION...1 2.0 RISK MANAGEMENT FRAMEWORK...3 2.1 RISK MANAGEMENT

More information

External Supplier Control Requirements

External Supplier Control Requirements External Supplier Control s Cyber Security For Suppliers Categorised as Low Cyber Risk 1. Asset Protection and System Configuration Barclays Data and the assets or systems storing or processing it must

More information

Frequently Asked Questions: Notice on Technology Risk Management

Frequently Asked Questions: Notice on Technology Risk Management Frequently Asked Questions: Notice on Technology Risk Management Q1: Which categories of financial institutions ("FIs") are subject to the Notice on Technology Risk Management ( Notice )? A1: The FIs to

More information

Data Security Incident Response Plan. [Insert Organization Name]

Data Security Incident Response Plan. [Insert Organization Name] Data Security Incident Response Plan Dated: [Month] & [Year] [Insert Organization Name] 1 Introduction Purpose This data security incident response plan provides the framework to respond to a security

More information

Operational Risk Publication Date: May 2015. 1. Operational Risk... 3

Operational Risk Publication Date: May 2015. 1. Operational Risk... 3 OPERATIONAL RISK Contents 1. Operational Risk... 3 1.1 Legislation... 3 1.2 Guidance... 3 1.3 Risk management process... 4 1.4 Risk register... 7 1.5 EBA Guidelines on the Security of Internet Payments...

More information

External Supplier Control Requirements

External Supplier Control Requirements External Supplier Control Requirements Cyber Security For Suppliers Categorised as High Cyber Risk Cyber Security Requirement Description Why this is important 1. Asset Protection and System Configuration

More information

Please note this policy is mandatory and staff are required to adhere to the content

Please note this policy is mandatory and staff are required to adhere to the content Policy ICT Security Please note this policy is mandatory and staff are required to adhere to the content Summary DECD is committed to ensuring its information is appropriately managed according to the

More information

SWAP EXECUTION FACILITY OPERATIONAL CAPABILITY TECHNOLOGY QUESTIONNAIRE

SWAP EXECUTION FACILITY OPERATIONAL CAPABILITY TECHNOLOGY QUESTIONNAIRE SWAP EXECUTION FACILITY OPERATIONAL CAPABILITY TECHNOLOGY QUESTIONNAIRE Please provide all relevant documents responsive to the information requests listed within each area below. In addition to the specific

More information

REGULATIONS FOR THE SECURITY OF INTERNET BANKING

REGULATIONS FOR THE SECURITY OF INTERNET BANKING REGULATIONS FOR THE SECURITY OF INTERNET BANKING PAYMENT SYSTEMS DEPARTMENT STATE BANK OF PAKISTAN Table of Contents PREFACE... 3 DEFINITIONS... 4 1. SCOPE OF THE REGULATIONS... 6 2. INTERNET BANKING SECURITY

More information

IT OUTSOURCING SECURITY

IT OUTSOURCING SECURITY IT OUTSOURCING SECURITY February 2008 The Government of the Hong Kong Special Administrative Region The contents of this document remain the property of, and may not be reproduced in whole or in part without

More information

University of Aberdeen Information Security Policy

University of Aberdeen Information Security Policy University of Aberdeen Information Security Policy Contents Introduction to Information Security... 1 How can information be protected?... 1 1. Information Security Policy... 3 Subsidiary Policy details:...

More information

LAMAR STATE COLLEGE - ORANGE INFORMATION RESOURCES SECURITY MANUAL. for INFORMATION RESOURCES

LAMAR STATE COLLEGE - ORANGE INFORMATION RESOURCES SECURITY MANUAL. for INFORMATION RESOURCES LAMAR STATE COLLEGE - ORANGE INFORMATION RESOURCES SECURITY MANUAL for INFORMATION RESOURCES Updated: June 2007 Information Resources Security Manual 1. Purpose of Security Manual 2. Audience 3. Acceptable

More information

Supplier Security Assessment Questionnaire

Supplier Security Assessment Questionnaire HALKYN CONSULTING LTD Supplier Security Assessment Questionnaire Security Self-Assessment and Reporting This questionnaire is provided to assist organisations in conducting supplier security assessments.

More information

FINAL May 2005. Guideline on Security Systems for Safeguarding Customer Information

FINAL May 2005. Guideline on Security Systems for Safeguarding Customer Information FINAL May 2005 Guideline on Security Systems for Safeguarding Customer Information Table of Contents 1 Introduction 1 1.1 Purpose of Guideline 1 2 Definitions 2 3 Internal Controls and Procedures 2 3.1

More information

OPERATIONAL CAPABILITY TECHNOLOGY QUESTIONNAIRE

OPERATIONAL CAPABILITY TECHNOLOGY QUESTIONNAIRE OPERATIONAL CAPABILITY TECHNOLOGY QUESTIONNAIRE Please provide all relevant documents responsive to the information requests listed within each area below. In addition to the specific documents requested,

More information

Appendix. Key Areas of Concern. i. Inadequate coverage of cybersecurity risk assessment exercises

Appendix. Key Areas of Concern. i. Inadequate coverage of cybersecurity risk assessment exercises Appendix Key Areas of Concern i. Inadequate coverage of cybersecurity risk assessment exercises The scope coverage of cybersecurity risk assessment exercises, such as cybersecurity control gap analysis

More information

ISO27001 Controls and Objectives

ISO27001 Controls and Objectives Introduction This reference document for the University of Birmingham lists the control objectives, specific controls and background information, as given in Annex A to ISO/IEC 27001:2005. As such, the

More information

COMPLIANCE CHECKLIST...

COMPLIANCE CHECKLIST... : Monetary Authority of Singapore COMPLIANCE CHECKLIST FOR INTERNET BANKING AND TECHNOLOGY RISK MAGEMENT GUIDELINES 3.0 TABLE OF CONTENTS SECTION A COMPLIANCE CHECKLIST... 1 B DESCRIPTION OF REMEDIAL ACTION...

More information

Newcastle University Information Security Procedures Version 3

Newcastle University Information Security Procedures Version 3 Newcastle University Information Security Procedures Version 3 A Information Security Procedures 2 B Business Continuity 3 C Compliance 4 D Outsourcing and Third Party Access 5 E Personnel 6 F Operations

More information

Attachment A. Identification of Risks/Cybersecurity Governance

Attachment A. Identification of Risks/Cybersecurity Governance Attachment A Identification of Risks/Cybersecurity Governance 1. For each of the following practices employed by the Firm for management of information security assets, please provide the month and year

More information

Information Technology Engineers Examination. Information Security Specialist Examination. (Level 4) Syllabus

Information Technology Engineers Examination. Information Security Specialist Examination. (Level 4) Syllabus Information Technology Engineers Examination Information Security Specialist Examination (Level 4) Syllabus Details of Knowledge and Skills Required for the Information Technology Engineers Examination

More information

GOVERNANCE AND SECURITY BEST PRACTICES FOR PAYMENT PROCESSORS

GOVERNANCE AND SECURITY BEST PRACTICES FOR PAYMENT PROCESSORS GOVERNANCE AND SECURITY BEST PRACTICES FOR PAYMENT PROCESSORS A White Paper by i2c, Inc. 1300 Island Drive Suite 105 Redwood City, CA 94065 USA +1 650-593-5400 sales@i2cinc.com www.i2cinc.com Table of

More information

University of Sunderland Business Assurance Information Security Policy

University of Sunderland Business Assurance Information Security Policy University of Sunderland Business Assurance Information Security Policy Document Classification: Public Policy Reference Central Register Policy Reference Faculty / Service IG 003 Policy Owner Assistant

More information

Information Security Policies. Version 6.1

Information Security Policies. Version 6.1 Information Security Policies Version 6.1 Information Security Policies Contents: 1. Information Security page 3 2. Business Continuity page 5 3. Compliance page 6 4. Outsourcing and Third Party Access

More information

SANS Top 20 Critical Controls for Effective Cyber Defense

SANS Top 20 Critical Controls for Effective Cyber Defense WHITEPAPER SANS Top 20 Critical Controls for Cyber Defense SANS Top 20 Critical Controls for Effective Cyber Defense JANUARY 2014 SANS Top 20 Critical Controls for Effective Cyber Defense Summary In a

More information

TASK -040. TDSP Web Portal Project Cyber Security Standards Best Practices

TASK -040. TDSP Web Portal Project Cyber Security Standards Best Practices Page 1 of 10 TSK- 040 Determine what PCI, NERC CIP cyber security standards are, which are applicable, and what requirements are around them. Find out what TRE thinks about the NERC CIP cyber security

More information

Polish Financial Supervision Authority. Guidelines

Polish Financial Supervision Authority. Guidelines Polish Financial Supervision Authority Guidelines on the Management of Information Technology and ICT Environment Security for Insurance and Reinsurance Undertakings Warsaw, 16 December 2014 Table of Contents

More information

IT Best Practices Audit TCS offers a wide range of IT Best Practices Audit content covering 15 subjects and over 2200 topics, including:

IT Best Practices Audit TCS offers a wide range of IT Best Practices Audit content covering 15 subjects and over 2200 topics, including: IT Best Practices Audit TCS offers a wide range of IT Best Practices Audit content covering 15 subjects and over 2200 topics, including: 1. IT Cost Containment 84 topics 2. Cloud Computing Readiness 225

More information

HIPAA CRITICAL AREAS TECHNICAL SECURITY FOCUS FOR CLOUD DEPLOYMENT

HIPAA CRITICAL AREAS TECHNICAL SECURITY FOCUS FOR CLOUD DEPLOYMENT HIPAA CRITICAL AREAS TECHNICAL SECURITY FOCUS FOR CLOUD DEPLOYMENT A Review List This paper was put together with Security in mind, ISO, and HIPAA, for guidance as you move into a cloud deployment Dr.

More information

Security Controls for the Autodesk 360 Managed Services

Security Controls for the Autodesk 360 Managed Services Autodesk Trust Center Security Controls for the Autodesk 360 Managed Services Autodesk strives to apply the operational best practices of leading cloud-computing providers around the world. Sound practices

More information

Data Protection Act 1998. Guidance on the use of cloud computing

Data Protection Act 1998. Guidance on the use of cloud computing Data Protection Act 1998 Guidance on the use of cloud computing Contents Overview... 2 Introduction... 2 What is cloud computing?... 3 Definitions... 3 Deployment models... 4 Service models... 5 Layered

More information

Domain 1 The Process of Auditing Information Systems

Domain 1 The Process of Auditing Information Systems Certified Information Systems Auditor (CISA ) Certification Course Description Our 5-day ISACA Certified Information Systems Auditor (CISA) training course equips information professionals with the knowledge

More information

www.pwc.com/sg Technology Risk Management Are you ready?

www.pwc.com/sg Technology Risk Management Are you ready? www.pwc.com/sg Technology Risk Management Are you ready? Contents Food For Thought... Questions 2 Guidelines & Notice New technology risk management guidelines and notice impact: All financial institutions

More information

Oracle Maps Cloud Service Enterprise Hosting and Delivery Policies Effective Date: October 1, 2015 Version 1.0

Oracle Maps Cloud Service Enterprise Hosting and Delivery Policies Effective Date: October 1, 2015 Version 1.0 Oracle Maps Cloud Service Enterprise Hosting and Delivery Policies Effective Date: October 1, 2015 Version 1.0 Unless otherwise stated, these Oracle Maps Cloud Service Enterprise Hosting and Delivery Policies

More information

Business Continuity Planning and Disaster Recovery Planning

Business Continuity Planning and Disaster Recovery Planning 4 Business Continuity Planning and Disaster Recovery Planning Basic Concepts 1. Business Continuity Management: Business Continuity means maintaining the uninterrupted availability of all key business

More information

Head of Information & Communications Technology Responsible work team: ICT Security. Key point summary... 2

Head of Information & Communications Technology Responsible work team: ICT Security. Key point summary... 2 Policy Procedure Information security policy Policy number: 442 Old instruction number: MAN:F005:a1 Issue date: 24 August 2006 Reviewed as current: 11 July 2014 Owner: Head of Information & Communications

More information

INFORMATION SECURITY MANAGEMENT SYSTEM. Version 1c

INFORMATION SECURITY MANAGEMENT SYSTEM. Version 1c INFORMATION SECURITY MANAGEMENT SYSTEM Version 1c Revised April 2011 CONTENTS Introduction... 5 1 Security Policy... 7 1.1 Information Security Policy... 7 1.2 Scope 2 Security Organisation... 8 2.1 Information

More information

Appendix J: Strengthening the Resilience of Outsourced Technology Services

Appendix J: Strengthening the Resilience of Outsourced Technology Services Appendix J: Strengthening the Resilience of Outsourced Technology Services Background and Purpose Many financial institutions depend on third-party service providers to perform or support critical operations.

More information

Ohio Supercomputer Center

Ohio Supercomputer Center Ohio Supercomputer Center IT Business Continuity Planning No: Effective: OSC-13 06/02/2009 Issued By: Kevin Wohlever Director of Supercomputer Operations Published By: Ohio Supercomputer Center Original

More information

Information security controls. Briefing for clients on Experian information security controls

Information security controls. Briefing for clients on Experian information security controls Information security controls Briefing for clients on Experian information security controls Introduction Security sits at the core of Experian s operations. The vast majority of modern organisations face

More information

Virginia Commonwealth University School of Medicine Information Security Standard

Virginia Commonwealth University School of Medicine Information Security Standard Virginia Commonwealth University School of Medicine Information Security Standard Title: Scope: Business Continuity Management Standard for IT Systems This standard is applicable to all VCU School of Medicine

More information

Music Recording Studio Security Program Security Assessment Version 1.1

Music Recording Studio Security Program Security Assessment Version 1.1 Music Recording Studio Security Program Security Assessment Version 1.1 DOCUMENTATION, RISK MANAGEMENT AND COMPLIANCE PERSONNEL AND RESOURCES ASSET MANAGEMENT PHYSICAL SECURITY IT SECURITY TRAINING AND

More information

Passing PCI Compliance How to Address the Application Security Mandates

Passing PCI Compliance How to Address the Application Security Mandates Passing PCI Compliance How to Address the Application Security Mandates The Payment Card Industry Data Security Standards includes several requirements that mandate security at the application layer. These

More information

State of Oregon. State of Oregon 1

State of Oregon. State of Oregon 1 State of Oregon State of Oregon 1 Table of Contents 1. Introduction...1 2. Information Asset Management...2 3. Communication Operations...7 3.3 Workstation Management... 7 3.9 Log management... 11 4. Information

More information

ISO 27001 Controls and Objectives

ISO 27001 Controls and Objectives ISO 27001 s and Objectives A.5 Security policy A.5.1 Information security policy Objective: To provide management direction and support for information security in accordance with business requirements

More information

Managing internet security

Managing internet security Managing internet security GOOD PRACTICE GUIDE Contents About internet security 2 What are the key components of an internet system? 3 Assessing internet security 4 Internet security check list 5 Further

More information

FEDERAL HOUSING FINANCE AGENCY ADVISORY BULLETIN AB 2014-05. Cyber Risk Management Guidance. Purpose

FEDERAL HOUSING FINANCE AGENCY ADVISORY BULLETIN AB 2014-05. Cyber Risk Management Guidance. Purpose FEDERAL HOUSING FINANCE AGENCY ADVISORY BULLETIN AB 2014-05 Cyber Risk Management Guidance Purpose This advisory bulletin provides Federal Housing Finance Agency (FHFA) guidance on cyber risk management.

More information

Cyber Security Incident Handling Policy. Information Technology Services Center (ITSC) of The Hong Kong University of Science and Technology

Cyber Security Incident Handling Policy. Information Technology Services Center (ITSC) of The Hong Kong University of Science and Technology Cyber Security Incident Handling Policy Information Technology Services Center (ITSC) of The Hong Kong University of Science and Technology Date: Oct 9, 2015 i Document Control Document Owner Classification

More information

OUTSOURCING INVOLVING SHARED COMPUTING SERVICES (INCLUDING CLOUD) 6 July 2015

OUTSOURCING INVOLVING SHARED COMPUTING SERVICES (INCLUDING CLOUD) 6 July 2015 OUTSOURCING INVOLVING SHARED COMPUTING SERVICES (INCLUDING CLOUD) 6 July 2015 Disclaimer and Copyright While APRA endeavours to ensure the quality of this publication, it does not accept any responsibility

More information

STRATEGIC POLICY REQUIRED HARDWARE, SOFTWARE AND CONFIGURATION STANDARDS

STRATEGIC POLICY REQUIRED HARDWARE, SOFTWARE AND CONFIGURATION STANDARDS Policy: Title: Status: ISP-S9 Use of Computers Policy Revised Information Security Policy Documentation STRATEGIC POLICY 1. Introduction 1.1. This information security policy document contains high-level

More information

GUIDANCE NOTE FOR DEPOSIT-TAKERS. Operational Risk Management. March 2012

GUIDANCE NOTE FOR DEPOSIT-TAKERS. Operational Risk Management. March 2012 GUIDANCE NOTE FOR DEPOSIT-TAKERS Operational Risk Management March 2012 Version 1.0 Contents Page No 1 Introduction 2 2 Overview 3 Operational risk - fundamental principles and governance 3 Fundamental

More information

The President s Critical Infrastructure Protection Board. Office of Energy Assurance U.S. Department of Energy 202/ 287-1808

The President s Critical Infrastructure Protection Board. Office of Energy Assurance U.S. Department of Energy 202/ 287-1808 cover_comp_01 9/9/02 5:01 PM Page 1 For further information, please contact: The President s Critical Infrastructure Protection Board Office of Energy Assurance U.S. Department of Energy 202/ 287-1808

More information

SUBJECT: SECURITY OF ELECTRONIC MEDICAL RECORDS COMPLIANCE WITH THE HEALTH INSURANCE PORTABILITY AND ACCOUNTABILITY ACT OF 1996 (HIPAA)

SUBJECT: SECURITY OF ELECTRONIC MEDICAL RECORDS COMPLIANCE WITH THE HEALTH INSURANCE PORTABILITY AND ACCOUNTABILITY ACT OF 1996 (HIPAA) UNIVERSITY OF PITTSBURGH POLICY SUBJECT: SECURITY OF ELECTRONIC MEDICAL RECORDS COMPLIANCE WITH THE HEALTH INSURANCE PORTABILITY AND ACCOUNTABILITY ACT OF 1996 (HIPAA) DATE: March 18, 2005 I. SCOPE This

More information

CENTRAL BANK OF KENYA (CBK) PRUDENTIAL GUIDELINE ON BUSINESS CONTINUITY MANAGEMENT (BCM) FOR INSTITUTIONS LICENSED UNDER THE BANKING ACT

CENTRAL BANK OF KENYA (CBK) PRUDENTIAL GUIDELINE ON BUSINESS CONTINUITY MANAGEMENT (BCM) FOR INSTITUTIONS LICENSED UNDER THE BANKING ACT CENTRAL BANK OF KENYA (CBK) PRUDENTIAL GUIDELINE ON BUSINESS CONTINUITY MANAGEMENT (BCM) FOR INSTITUTIONS LICENSED UNDER THE BANKING ACT JANUARY 2008 GUIDELINE ON BUSINESS CONTINUITY GUIDELINE CBK/PG/14

More information

OCIE CYBERSECURITY INITIATIVE

OCIE CYBERSECURITY INITIATIVE Topic: Cybersecurity Examinations Key Takeaways: OCIE will be conducting examinations of more than 50 registered brokerdealers and registered investment advisers, focusing on areas related to cybersecurity.

More information

Unified Security Anywhere HIPAA COMPLIANCE ACHIEVING HIPAA COMPLIANCE WITH MASERGY PROFESSIONAL SERVICES

Unified Security Anywhere HIPAA COMPLIANCE ACHIEVING HIPAA COMPLIANCE WITH MASERGY PROFESSIONAL SERVICES Unified Security Anywhere HIPAA COMPLIANCE ACHIEVING HIPAA COMPLIANCE WITH MASERGY PROFESSIONAL SERVICES HIPAA COMPLIANCE Achieving HIPAA Compliance with Security Professional Services The Health Insurance

More information

Autodesk PLM 360 Security Whitepaper

Autodesk PLM 360 Security Whitepaper Autodesk PLM 360 Autodesk PLM 360 Security Whitepaper May 1, 2015 trust.autodesk.com Contents Introduction... 1 Document Purpose... 1 Cloud Operations... 1 High Availability... 1 Physical Infrastructure

More information

RS Official Gazette, No 23/2013 and 113/2013

RS Official Gazette, No 23/2013 and 113/2013 RS Official Gazette, No 23/2013 and 113/2013 Pursuant to Article 15, paragraph 1 and Article 63, paragraph 2 of the Law on the National Bank of Serbia (RS Official Gazette, Nos 72/2003, 55/2004, 85/2005

More information

Data Management Policies. Sage ERP Online

Data Management Policies. Sage ERP Online Sage ERP Online Sage ERP Online Table of Contents 1.0 Server Backup and Restore Policy... 3 1.1 Objectives... 3 1.2 Scope... 3 1.3 Responsibilities... 3 1.4 Policy... 4 1.5 Policy Violation... 5 1.6 Communication...

More information

Cloud Computing and Records Management

Cloud Computing and Records Management GPO Box 2343 Adelaide SA 5001 Tel (+61 8) 8204 8773 Fax (+61 8) 8204 8777 DX:336 srsarecordsmanagement@sa.gov.au www.archives.sa.gov.au Cloud Computing and Records Management June 2015 Version 1 Version

More information

Regulations on Information Systems Security. I. General Provisions

Regulations on Information Systems Security. I. General Provisions Riga, 7 July 2015 Regulations No 112 (Meeting of the Board of the Financial and Capital Market Commission Min. No 25; paragraph 2) Regulations on Information Systems Security Issued in accordance with

More information

SECURITY. Risk & Compliance Services

SECURITY. Risk & Compliance Services SECURITY Risk & Compliance s V1 8/2010 Risk & Compliances s Risk & compliance services Summary Summary Trace3 offers a full and complete line of security assessment services designed to help you minimize

More information

Security Overview. BlackBerry Corporate Infrastructure

Security Overview. BlackBerry Corporate Infrastructure Security Overview BlackBerry Corporate Infrastructure Published: 2015-04-23 SWD-20150423095908892 Contents Introduction... 5 History... 6 BlackBerry policies...7 Security organizations...8 Corporate Security

More information

HIPAA Security. 2 Security Standards: Administrative Safeguards. Security Topics

HIPAA Security. 2 Security Standards: Administrative Safeguards. Security Topics HIPAA Security SERIES Security Topics 1. Security 101 for Covered Entities 5. 2. Security Standards - Organizational, Security Policies Standards & Procedures, - Administrative and Documentation Safeguards

More information

Decision on adequate information system management. (Official Gazette 37/2010)

Decision on adequate information system management. (Official Gazette 37/2010) Decision on adequate information system management (Official Gazette 37/2010) Pursuant to Article 161, paragraph (1), item (3) of the Credit Institutions Act (Official Gazette 117/2008, 74/2009 and 153/2009)

More information

HIPAA Security Alert

HIPAA Security Alert Shipman & Goodwin LLP HIPAA Security Alert July 2008 EXECUTIVE GUIDANCE HIPAA SECURITY COMPLIANCE How would your organization s senior management respond to CMS or OIG inquiries about health information

More information

High Level Cyber Security Assessment 2/1/2012. Assessor: J. Doe

High Level Cyber Security Assessment 2/1/2012. Assessor: J. Doe 2/1/2012 Assessor: J. Doe Disclaimer This report is provided as is for informational purposes only. The Department of Homeland Security (DHS) does not provide any warranties of any kind regarding any information

More information

Tailored Technologies LLC

Tailored Technologies LLC 685 Third Avenue New York, NY 10017 Tel: (212) 503-6300 Fax: (212) 503-6312 Date: January 9, 2014 To: The Audit File of the Hugh L. Carey Battery Park City Authority From: Tailored Technology Observations

More information

Office of Inspector General

Office of Inspector General DEPARTMENT OF HOMELAND SECURITY Office of Inspector General Security Weaknesses Increase Risks to Critical United States Secret Service Database (Redacted) Notice: The Department of Homeland Security,

More information

Cisco Security Optimization Service

Cisco Security Optimization Service Cisco Security Optimization Service Proactively strengthen your network to better respond to evolving security threats and planned and unplanned events. Service Overview Optimize Your Network for Borderless

More information

Committee on Payments and Market Infrastructures. Board of the International Organization of Securities Commissions

Committee on Payments and Market Infrastructures. Board of the International Organization of Securities Commissions Committee on Payments and Market Infrastructures Board of the International Organization of Securities Commissions Principles for financial market infrastructures: Assessment methodology for the oversight

More information

Supplier Information Security Addendum for GE Restricted Data

Supplier Information Security Addendum for GE Restricted Data Supplier Information Security Addendum for GE Restricted Data This Supplier Information Security Addendum lists the security controls that GE Suppliers are required to adopt when accessing, processing,

More information

HIGH-RISK SECURITY VULNERABILITIES IDENTIFIED DURING REVIEWS OF INFORMATION TECHNOLOGY GENERAL CONTROLS

HIGH-RISK SECURITY VULNERABILITIES IDENTIFIED DURING REVIEWS OF INFORMATION TECHNOLOGY GENERAL CONTROLS Department of Health and Human Services OFFICE OF INSPECTOR GENERAL HIGH-RISK SECURITY VULNERABILITIES IDENTIFIED DURING REVIEWS OF INFORMATION TECHNOLOGY GENERAL CONTROLS AT STATE MEDICAID AGENCIES Inquiries

More information

Addressing Cloud Computing Security Considerations

Addressing Cloud Computing Security Considerations Addressing Cloud Computing Security Considerations with Microsoft Office 365 Protect more Contents 2 Introduction 3 Key Security Considerations 4 Office 365 Service Stack 5 ISO Certifications for the Microsoft

More information

LEEDS BECKETT UNIVERSITY. Information Security Policy. 1.0 Introduction

LEEDS BECKETT UNIVERSITY. Information Security Policy. 1.0 Introduction LEEDS BECKETT UNIVERSITY Information Security Policy 1.0 Introduction 1.1 Information in all of its forms is crucial to the effective functioning and good governance of our University. We are committed

More information

Build (develop) and document Acceptance Transition to production (installation) Operations and maintenance support (postinstallation)

Build (develop) and document Acceptance Transition to production (installation) Operations and maintenance support (postinstallation) It is a well-known fact in computer security that security problems are very often a direct result of software bugs. That leads security researches to pay lots of attention to software engineering. The

More information

Information Security Risk Assessment Checklist. A High-Level Tool to Assist USG Institutions with Risk Analysis

Information Security Risk Assessment Checklist. A High-Level Tool to Assist USG Institutions with Risk Analysis Information Security Risk Assessment Checklist A High-Level Tool to Assist USG Institutions with Risk Analysis Updated Oct 2008 Introduction Information security is an important issue for the University

More information

Cybersecurity and internal audit. August 15, 2014

Cybersecurity and internal audit. August 15, 2014 Cybersecurity and internal audit August 15, 2014 arket insights: what we are seeing so far? 60% of organizations see increased risk from using social networking, cloud computing and personal mobile devices

More information

Information Security Services

Information Security Services Information Security Services Information Security In 2013, Symantec reported a 62% increase in data breaches over 2012. These data breaches had tremendous impacts on many companies, resulting in intellectual

More information

DBC 999 Incident Reporting Procedure

DBC 999 Incident Reporting Procedure DBC 999 Incident Reporting Procedure Signed: Chief Executive Introduction This procedure is intended to identify the actions to be taken in the event of a security incident or breach, and the persons responsible

More information

Managing IT Security with Penetration Testing

Managing IT Security with Penetration Testing Managing IT Security with Penetration Testing Introduction Adequately protecting an organization s information assets is a business imperative one that requires a comprehensive, structured approach to

More information

Third Party Security Requirements Policy

Third Party Security Requirements Policy Overview This policy sets out the requirements expected of third parties to effectively protect BBC information. Audience Owner Contacts This policy applies to all third parties and staff, including contractors,

More information

Five keys to a more secure data environment

Five keys to a more secure data environment Five keys to a more secure data environment A holistic approach to data infrastructure security Compliance professionals know better than anyone how compromised data can lead to financial and reputational

More information

Compliance Guide ISO 27002. Compliance Guide. September 2015. Contents. Introduction 1. Detailed Controls Mapping 2.

Compliance Guide ISO 27002. Compliance Guide. September 2015. Contents. Introduction 1. Detailed Controls Mapping 2. ISO 27002 Compliance Guide September 2015 Contents Compliance Guide 01 02 03 Introduction 1 Detailed Controls Mapping 2 About Rapid7 7 01 INTRODUCTION If you re looking for a comprehensive, global framework

More information

PAPER-6 PART-1 OF 5 CA A.RAFEQ, FCA

PAPER-6 PART-1 OF 5 CA A.RAFEQ, FCA 1 Chapter-4: Business Continuity Planning and Disaster Recovery Planning PAPER-6 PART-1 OF 5 CA A.RAFEQ, FCA Learning Objectives 2 To understand the concept of Business Continuity Management To understand

More information

ELECTRONIC INFORMATION SECURITY A.R.

ELECTRONIC INFORMATION SECURITY A.R. A.R. Number: 2.6 Effective Date: 2/1/2009 Page: 1 of 7 I. PURPOSE In recognition of the critical role that electronic information systems play in City of Richmond (COR) business activities, this policy

More information

PATCH MANAGEMENT. February 2008. The Government of the Hong Kong Special Administrative Region

PATCH MANAGEMENT. February 2008. The Government of the Hong Kong Special Administrative Region PATCH MANAGEMENT February 2008 The Government of the Hong Kong Special Administrative Region The contents of this document remain the property of, and may not be reproduced in whole or in part without

More information

Cloud Software Services for Schools

Cloud Software Services for Schools Cloud Software Services for Schools Supplier self-certification statements with service and support commitments Please insert supplier details below Supplier name Address Contact name Contact email Contact

More information