<?xml version="1.0"?>
<standard status="released">
<standardinfo>
<title>Data Protection European Union Security Standard</title>
<titleabbrev>LCZ-DPA</titleabbrev>
<edition>1.1</edition>
<pubdate>16 May 2009</pubdate>
<abstract>
<para>This document specifies technical and non-technical security policy for the European Union Data Protection Directive as implemented by the UK Data Protection Act 1998.
</para>
</abstract>
<revhistory>
<revision>
<revnumber>1.1</revnumber>
<date>16 May 2009</date>
<authorinitials>FOD</authorinitials>
<revremark>Revised for re-release</revremark>
</revision>
<revision>
<revnumber>1.0</revnumber>
<date>18 June 2003</date>
<authorinitials>LCZ</authorinitials>
<revremark>Initial Draft for public release</revremark>
</revision>
</revhistory>
<copyright>
<year>2001</year><year>2002</year><year>2003</year><year>2009</year>
<holder>Frank O'Dwyer</holder>
</copyright>
</standardinfo>
<intro>
<objectives>
<objective>To provide guidance to administators, developers, security personnel and data protection officers in implementing the UK Data Protection Act 1998.
</objective>
</objectives>
<scope>
<para>Controls specified in this document apply to all organisations who process personal data relating to citizens of the member states of the European Union.
</para>
<para>All of the organisation's information systems
that process personal data will be subject to the policies 
specified within this security standard. The policies will
be applied to both new and existing installations and should
also be applied to organised manual systems.
</para>
</scope>
<out-of-scope>
<para>Compliance with this standard will not provide <quote>in depth</quote> security architecture or intelligent security design guidance
to projects. As a consequence, for high impact or safety-critical business applications, additional guidance will still need to be 
sought from the Information Security team consultancy function. This standard is not a substitute for legal advice or a data protection officer. 
</para>
<para>Compliance with this standard does not negate the need for an overall security review 
of a proposed application. Contact the Information Security team if you are in doubt.
</para>
</out-of-scope>
<commonintrostuff/>
<relateddocs/>
<definitions>
<definition>
<para>An <quote>Information Asset</quote> equates to any computerised information system 
or component thereof and thus includes an application, an item of off the shelf software, hardware, media, 
a data item, a data item repository and associated communications networks.</para>
<para>The specification of 
the Information Asset in question will usually be given so that this document is unambiguous, except
where a control relates to any <quote>Information Asset</quote>. </para>
</definition>
<definition>
<para>The use of <quote>must</quote> or <quote>will</quote> indicates what the author considers to be a mandatory control.</para>
<para>However, whether the controls listed here are mandatory for your organisation is entirely at your organisation's discretion and
thus they should be interpreted as representing the strongest recommendation of the author.</para>
</definition>
<definition>
<para>The use of <quote>should</quote> or <quote>recommended</quote> or <quote>ought</quote> indicates
that the author believes that the controls in question are worthwhile and should be implemented unless such
an implementation is impossible, onerous or impractical. Again, the implementation of controls so recommended
in this document is entirely at your organisation's discretion.</para>
</definition>
</definitions>
</intro>
<controlchapter><title>Desktop Security Requirements</title>
<controlsection><title>Logical Access Controls</title>
</controlsection>
<controlsection><title>Security Management and Administration</title>
</controlsection>
<controlsection><title>Security Incident Reporting</title>
</controlsection>
<controlsection><title>Physical Access Controls</title>
</controlsection>
<controlsection><title>Protection from malicious software</title>
</controlsection>
</controlchapter>
<controlchapter><title>Portable and off site computing requirements</title>
<controlsection><title>Physical access controls</title>
</controlsection>
<controlsection><title>Security management and administration</title>
</controlsection>
<controlsection><title>General security points</title>
</controlsection>
<controlsection><title>Logical access controls</title>
</controlsection>
<controlsection><title>Protection from malicious software</title>
</controlsection>
</controlchapter>
<controlchapter><title>Network Security Requirements</title>
<controlsection><title>Data Back-up controls</title>
</controlsection>
<controlsection><title>Dialup Connection Security</title>
</controlsection>
<controlsection><title>Dialup Security Management Issues</title>
</controlsection>
<controlsection><title>Third Party Access - Customers</title>
</controlsection>
<controlsection><title>Access controls</title>
</controlsection>
<controlsection><title>Management Controls</title>
</controlsection>
<controlsection><title>Physical security controls</title>
</controlsection>
<controlsection><title>Network Devices</title>
</controlsection>
</controlchapter>
<controlchapter><title>Personnel Security</title>
<controlsection><title>Security in job descriptions</title>
</controlsection>
<controlsection><title>Reporting of security matters</title>
</controlsection>
<controlsection><title>Recruitment</title>
</controlsection>
<controlsection><title>Education and Awareness</title>
</controlsection>
</controlchapter>
<controlchapter><title>User Configuration</title>
<controlsection><title>User Administration</title>
</controlsection>
<controlsection><title>Default Accounts</title>
</controlsection>
<controlsection><title>Roles, Views, and Access Control</title>
</controlsection>
<controlsection><title>Privileges</title>
</controlsection>
<controlsection><title>Authentication/Password Configuration</title>
</controlsection>
</controlchapter>
<controlchapter><title>Security Compliance</title>
<controlsection><title>Security Compliance Checking</title>
</controlsection>
<controlsection><title>Security Management</title>
<control level="baseline" techversion="Any" title="Ensure that all new uses of personal data by an application are made known to the data protection officer and notified to the data subjects" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-OFFICE-3" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that all new uses of personal data by an application are made known to the data protection officer and notified to the data subjects</policy-statement>
<checklist-question>Has it been ensured that all new uses of personal data by an application are made known to the data protection officer and notified to the data subjects?</checklist-question>
<howto>
<step>Identify all functional uses of personal data</step>
<step>Make these known to the data protection officer</step>
<step>Where appropriate notify the data subjects of the new uses</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that all uses of personal data by a new application are made known to the data protection officer" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-OFFICE-2" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that all uses of personal data by a new application are made known to the data protection officer</policy-statement>
<checklist-question>Have you ensured that all uses of personal data by a new application have been made known to the data protection officer?</checklist-question>
<howto>
<step>Identify all functional uses of personal data</step>
<step>Make these known to the data protection officer</step>
<step>Where necessary update the registration of your organisation</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
</risks-addressed>
</control>
<control level="above baseline" techversion="Any" title="Ensure that explicit consent is given by the data subjects for procesing of sensitive personal data originally obtained for a different purpose." environment="Any" pleading="mandatory" versionMaj="1" id="DPA-OFFICE-4" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="above baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that explicit consent is given by the data subjects for processing of sensitive personal data originally obtained for a different purpose.</policy-statement>
<checklist-question>Has it been ensured that explicit consent has been given by the data subjects for processing of sensitive personal data originally obtained for a different purpose?</checklist-question>
<howto>
<step>Identify all functional uses of sensitive personal data</step>
<step>Make these known to the data protection officer</step>
<step>Identify any different uses that are now being made of the personal data</step>
<step>Seek explicit permission from the data subjects regarding these new uses</step>
<step>Exclude those data subjects from the application database who do not provide explicit permission</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure you have appointed a data protection officer to manage compliance with data protection legislation." environment="Any" pleading="mandatory" versionMaj="1" id="DPA-OFFICE-1" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure you have appointed a data protection officer to manage compliance with data protection legislation.</policy-statement>
<checklist-question>Have you have appointed a data protection officer to manage compliance with data protection legislation?</checklist-question>
<howto>
<step>Appoint an appropriate individual to act as the Data Protection Officer</step>
<step>This may be a part time role, full time or even a team of people depending on the size of your organisation and the nature of it&apos;s activities</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
</risks-addressed>
</control>
</controlsection>
</controlchapter>
<controlchapter><title>Software Requirements</title>
<controlsection><title>Software legislation and compliance</title>
</controlsection>
<controlsection><title>Software acquisition and implementation</title>
</controlsection>
</controlchapter>
<controlchapter><title>Network Security Configuration</title>
<controlsection><title>Network Interface Considerations</title>
</controlsection>
<controlsection><title>Internet Considerations</title>
</controlsection>
</controlchapter>
<controlchapter><title>Asset Security Requirements</title>
<controlsection><title>Ownership, Accountability and Inventories</title>
</controlsection>
<controlsection><title>Classification Labelling</title>
</controlsection>
</controlchapter>
<controlchapter><title>Compliance</title>
<controlsection><title>The Companies Act 1985</title>
</controlsection>
<controlsection><title>Data Protection Act 1998</title>
</controlsection>
<controlsection><title>Computer Misuse Act 1990</title>
</controlsection>
<controlsection><title>Information Security Policy</title>
</controlsection>
</controlchapter>
<controlchapter><title>Physical Security Requirements</title>
<controlsection><title>Outer perimeter - public access space</title>
</controlsection>
<controlsection><title>Inner perimeter - general space</title>
</controlsection>
</controlchapter>
<controlchapter><title>Internet/Email Security Requirements</title>
<controlsection><title>General Internet security requirements</title>
</controlsection>
</controlchapter>
<controlchapter><title>Configuration</title>
<controlsection><title>Files and File Permissions</title>
</controlsection>
<controlsection><title>Administration</title>
</controlsection>
<controlsection><title>Backups</title>
</controlsection>
</controlchapter>
<controlchapter><title>System Development and Maintenance Requirements</title>
<controlsection><title>General Software Requirements</title>
</controlsection>
<controlsection><title>Change Control Procedures</title>
</controlsection>
<controlsection><title>Application system security</title>
</controlsection>
<controlsection><title>Security requirements for Analysis and Specification</title>
</controlsection>
<controlsection><title>Test Data Security</title>
</controlsection>
<controlsection><title>Control of operational software</title>
</controlsection>
<controlsection><title>Security of electronic office systems</title>
</controlsection>
</controlchapter>
<controlchapter><title>Installation</title>
<controlsection><title>Setup Choices</title>
</controlsection>
</controlchapter>
<controlchapter><title>Auditing and Monitoring</title>
<controlsection><title>Events to be alerted in real-time</title>
</controlsection>
<controlsection><title>Audit log destination and format</title>
</controlsection>
<controlsection><title>Events to be audited</title>
<control level="baseline" techversion="Any" title="Personal data must be kept only as long as required for the purposes for which it is to be processed." environment="Any" pleading="mandatory" versionMaj="1" id="DPA-APP-11" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Auditing and Monitoring:Events to be audited" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Personal data must be kept only as long as required for the purposes for which it is to be processed.</policy-statement>
<checklist-question>Is personal data kept only as long as required for the purposes for which it is to be processed?</checklist-question>
<howto>
<step>Identify every item of personal data to be processed</step>
<step>For each data item determine a lifetime</step>
<step>Ensure that the personal data is deleted at the expiry of that lifetime</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that the application has an audit trail that captures all uses made of personal data" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-APP-10" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Auditing and Monitoring:Events to be audited" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that the application has an audit trail that captures all uses made of personal data</policy-statement>
<checklist-question>Does the application have an audit trail that captures all uses made of the personal data?</checklist-question>
<howto>
<step>Ensure that every application function that is used to read, write, change or delete personal data fields generates and audit record.</step>
<step>The audit record must contain at minimum the user id associated with the action, the date and time, the action itself and the source of the user login</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
<risk>Business information being subject to unauthorised to disclosure</risk>
<risk>Business information being subject to unauthorised modification</risk>
<risk>Business information being unavailable</risk>
</risks-addressed>
</control>
</controlsection>
</controlchapter>
<controlchapter><title>Other</title>
<control level="baseline" techversion="Any" title="Ensure that the data gathering methods employed by the application, such as forms, only gathers correct and relevant information when processing personal data." environment="Any" pleading="mandatory" versionMaj="1" id="DPA-APP-7" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that the data gathering methods employed by the application, such as forms, only gathers correct and relevant information when processing personal data.</policy-statement>
<checklist-question>Is it ensured that the data gathering methods employed by the application, such as forms, only gathers correct and relevant information when processing personal data?</checklist-question>
<howto>
<step>Ensure that only required data is collected</step>
<step>Ensure that only registered processing purposes of that data is performed</step>
<step>Ensure that data integrity checks are performed on the data to ensure that it is reasonable</step>
<step>Ensure that the other controls in this security stanhdard are adhered to.</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
<risk>Business information may be subject to unauthorised disclosure</risk>
<risk>Business information may be unavailable</risk>
<risk>Business information may be subject to a loss of integrity</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Outbound recipients of personal data must be identifiable within the application" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-APP-2" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that all outbound recipients of personal data from this application are identifiable in the application.</policy-statement>
<checklist-question>is it ensured that all outbound recipients of personal data from this application are identifiable in the application?</checklist-question>
<howto>
<step>Identify all of the personal data processed by the application</step>
<step>For each data item to determine all of the outbound recipients of the data</step>
<step>Ensure that the application logic is able to both display and report on the outbound recipients of the personal data</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
<risk>Business information may be subject to unauthorised disclosure</risk>
<risk>Business information may be unavailableh</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Cross border data transfers must be between states with equivalent data protection legislation" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-PROC-5" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that no personal data is transferred outside the European Union unless the destination country and any intermediate countries have adopted legislation that offers an equivalent or higher level of data protection.</policy-statement>
<checklist-question>Is it ensured that no personal data is transferred outside the European Union unless the destination and intermediate countries have adopted legislation that offers an equivalent or higher level of data protection?</checklist-question>
<howto>
<step>Identify non European Union destinations for personal data</step>
<step>Determine whether their data protection legislation offers similar protection as that afforded in EU member states</step>
<step>Where it does not, do not transfer the daa</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
<risk>Unauthorised disclosure of business information</risk>
<risk>Unauthorised modification of business information</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Processing must be adequate, relevant and not excessive" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-PROC-2" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that all personal data to be processed is adequate, relevant and not excessive in relation to the purposes for which it is processed.</policy-statement>
<checklist-question>Have you ensured that all personal data to be processed is adequate, relevant and not excessive in relation to the purposes for which it is processed?</checklist-question>
<howto>
<step>Collect only the personal data that you need </step>
<step>Process the personal data in accordance with your organisations registered uses</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that the data subjects are notified of the purposes for which the personal data has been acquired or collected" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-DATA-2" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that the data subjects are notified of the purposes for which the personal data has been acquired or collected</policy-statement>
<checklist-question>Do you ensure that the data subjects are notified of the purposes for which the personal data has been acquired or collected?</checklist-question>
<howto>
<step>On all collection forms include a section describing the uses that the personal data will be put to</step>
<step>Periodically notify the data subjects of the uses of personal data that has been collected.</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that the data gathering forms include a checkbox to indicate consent received from the data subject" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-APP-8" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that the data gathering forms include a checkbox to indicate that consent has been received from the data subject for the processing</policy-statement>
<checklist-question>Is it ensure that the data gathering forms include a checkbox to indicate that consent has been received from the data subject for the processing to take place?</checklist-question>
<howto>
<step>Include a consent field on the forms for the data subject to indicate whether consent has been obtained</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that the application only processes the minimum amount of personal data necessary to achieve the business objectives of the application. " environment="Any" pleading="mandatory" versionMaj="1" id="DPA-APP-9" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that the application only processes the minimum amount of personal data necessary to achieve the business objectives of the application.</policy-statement>
<checklist-question>Has it been ensured that the application only processes the minimum amount of personal data necessary to achieve the business objectives of the application?</checklist-question>
<howto>
<step>Verify that every field of personal data isjustified in relation to the registered purposes and the processing required.</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
<risk>Unauthorised disclosure of business information</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="All abbreviations used within the application must be viewable and reportable in an intelligible form" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-APP-12" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that the application includes definitions for all abbreviations or codes used in the application so as to allow data subjects to have relevant information disclosed in an intelligible form.</policy-statement>
<checklist-question>Has it been ensured that the application includes definitions of all abbreviations or codes used to allow data subjects to have relevant information disclosed in an intelligible form.</checklist-question>
<howto>
<step>Identify all abbreviations, acronyms, codes etc</step>
<step>For each one that is used ensure that when viewing or reporting data a means of eliciting the full meaning is available</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that all sources of personal data are identifiable within the application." environment="Any" pleading="mandatory" versionMaj="1" id="DPA-APP-1" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that all sources of personal data are identifiable within the application.</policy-statement>
<checklist-question>Is it ensured that all sources of personal data are identifiable within the application?</checklist-question>
<howto>
<step>Ensure that all fields or files that will contain personal data are identified</step>
<step>Ensure that for each data item to be stored that a source attribute is include</step>
<step>Ensure that the application logic has the ability to both display and report on the sources of data</step>
<step>Ensure that unknown sources of personal data are validated through a subject survey or deleted</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
<risk>Business information may be subject to a loss of integrity</risk>
<risk>Business information may be unavailable</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that personal data is subject to appropriate technical protection measures" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-PROC-3" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that all the personal data is subject to appropriate technical measures to protect against unauthorised or unlawful processing and accidental loss, destruction or damage.</policy-statement>
<checklist-question>Have you ensured that all personal data is subject to appropriate technical measures to protect against unauthorised or unlawful processing and accidental loss, destruction or damage.</checklist-question>
<howto>
<step>Perform a risk analysis against all applications or systems that process personal data</step>
<step>Define a technical security architecture in line with the results of the risk analysis</step>
<step>Retain the risk analysis documentation and reports to provide an audit trail of the reasoning behind the technical measures deployed</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
<risk>Business information may be subject to unauthorised disclosure</risk>
<risk>Business information may be subject to a loss of integrity</risk>
<risk>Business information may be unavailable</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Train employees to work within and understand their obligations under the Data Protection Act" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-PROC-6" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that employees dealing with the personal data processed by this application have been trained so as to understand the principles of the Data Protection Act and the impact that these principles have on the way they work.</policy-statement>
<checklist-question>Have employees that deal with the personal data processed by this application been trained so as to understand the principles of the Data Protection Act and the impact that these principles have on the way they work?</checklist-question>
<howto>
<step>Train the employees who handle/process personal data to understand the data protection act and how this impacts working practices.</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
<risk>Unauthorised disclosure of business information</risk>
<risk>Unauthorised modification of business information</risk>
<risk>Unauthorised loss of business information</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Personal data must be protected against unlawful processing" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-PROC-4" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that all the personal data is subject to appropriate organisational measures to protect against unauthorised or unlawful processing and accidental loss, destruction or damage.</policy-statement>
<checklist-question>Is the personal data subject to appropriate organisational measures to protect against unauthorised or unlawful processing and accidental loss, destruction or damage?</checklist-question>
<howto>
<step>Ensure that access to personal data is based upon requirements of a role and is authorised by the application or business process owner</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
<risk>Unauthorised disclosure of business information</risk>
<risk>Unauthorised modification of business information</risk>
<risk>Loss of availability of business information</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="The application design and documentation must include a clear description of the purposes for which personal data is being processed." environment="Any" pleading="mandatory" versionMaj="1" id="DPA-APP-5" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that the application design and documentation includes a clear description of the purposes for which personal data is being processed.</policy-statement>
<checklist-question>Does the application design and documentation include a clear description of the purposes for which personal data is being processed?</checklist-question>
<howto>
<step>Identify the application data to be processed</step>
<step>Identify the processes that are to be performed on the personal data</step>
<step>Ensure that the data and the processes to be performed are documented</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
<risk>Business information may be subject to unauthorised disclosure</risk>
<risk>Business information may be unavailable</risk>
<risk>Business information may be subject to a loss of integrity</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Personal data processed by an application must be subject to periodic maintenance" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-APP-4" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that a schedule of maintenance for the personal data that is processed by this application is developed and includes destruction and retention.</policy-statement>
<checklist-question>Has it been ensured that a schedule of maintenance for the personal data that is processed by this application has been developed that includes destruction and retention.</checklist-question>
<howto>
<step>Identify all of the personal data processed by the application</step>
<step>Create a schedule of periodic maintenance</step>
<step>Ensure the schedule includes validation</step>
<step>Ensure the schedule includes destruction of data that is no longer required to be held or data that is no longer correct and does not required to be held for historical purposes</step>
<step>Ensure that the schedule includes retention/archiving for personal data that must be kept for historic or regulatory reasons or otherwise for lawful processing</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
<risk>Business information may be subject to unauthorised disclosure</risk>
<risk>Business information may be unavailable</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that the application design both now and in future phases will result in processing of personal data that is both fair and lawful." environment="Any" pleading="mandatory" versionMaj="1" id="DPA-APP-6" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that the application design both now and in future phases will result in processing of personal data that is both fair and lawful.</policy-statement>
<checklist-question>Will the application design both now and in future phases result in processing of personal data that is both fair and lawful.</checklist-question>
<howto>
<step>Ensure the application design complies with the controls in this standard</step>
<step>Ensure that the application design complies with the requirements of your organisations legal department and data protection office</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
<risk>Business information may be subject to unauthorised disclosure</risk>
<risk>Business information may be unavailable</risk>
<risk>Business information may be subject to a loss of integrity</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Processing must be fair and lawful" environment="Any" pleading="mandatory" versionMaj="1" id="DPA-PROC-1" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that all personal data that is to be processed i.e. collected, organised, stored, retrieved, disclosed or destroyed is done so fairly and lawfully.</policy-statement>
<checklist-question>Ensure that all personal data that is to be processed i.e. collected, organised, stored, retrieved, disclosed or destroyed is done so fairly and lawfully.</checklist-question>
<howto>
<step>Ensure categories of data collected match that which are actually collected</step>
<step>Ensure that the uses of the data match the uses for which your organisation is registered.</step>
<step>Ensure that data subjects are aware of the data that your organisation collects about them</step>
<step>Ensure that data subjects are aware of the processing of the data that your organisation performs</step>
<step>Ensure that as a minimum you comply with all of the controls in this security standard</step>
<step>Ensure one of the following conditions are satisfied</step>
<step>- The data subject gives his or her consent to the processing or If the data subject is an employee or a prospective employee, ensure that the processing is necessary for the performance of a contract to which the employee is a party or for the taking of steps at the prospective employees request with a view to entering into a contract.</step>
<step>- The processing is necessary for compliance with a legal obligation.</step>
<step>- The processing is necessary to protect the interests of the data subject</step>
<step>- The processing is necessary in the public interest or in the exercise of official authority</step>
<step>- The processing is necessary for the purposes of the legitimate interests of the processing party except where these interests are overridden by the fundamental rights and freedom of the data subject. </step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that every category or type of personal data that your organisation processes is registered with the Data Protection registrar " environment="Any" pleading="mandatory" versionMaj="1" id="DPA-DATA-1" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that every category or type of personal data that your organisation processes is registered with the Data Protection registrar </policy-statement>
<checklist-question>Have you ensured that every category or type of personal data that your organisation processes is registered with the Data Protection registrar?</checklist-question>
<howto>
<step>Identify every category or type of personal data processed by your organisation</step>
<step>Register these data types with the data protection registrar</step>
<step>Put in place a process to ensure that this is maintained up to date</step>
<step>For a new application processing personal data perform a gap analysis to determine whether new categories of personal data are to be processed</step>
<step>Update your organisation&apos;s registration accordingly</step>
</howto>
<risks-addressed>
<risk>Non-compliance with legal requirements</risk>
<risk>Censure from the Data Protection Commission</risk>
<risk>Fines from the Data Protection Commission</risk>
</risks-addressed>
</control>
</controlchapter>
</standard>

