<?xml version="1.0"?>
<standard status="released">
<standardinfo>
<title>Application Service Provider Security Standard</title>
<titleabbrev>LCZ-ASP</titleabbrev>
<edition>1.1</edition>
<pubdate>16 May 2009</pubdate>
<abstract>
<para>This document specifies technical and non-technical security policy for ASP implementations and applies to any ASP service regardless of technology to be used.
</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>13 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 specify a security policy and standards for ASP delivered solutions.
</objective>
<objective>To provide guidance to administators, developers and security personnel in securely implementing ASP solutions.  
</objective>
</objectives>
<scope>
<para>
</para>
<para>
</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.  
</para>
<para>This is an ASP security policy. Controls specific to technologies used in the service are not 
defined here but will be the subject of additional standards. This document should also be read in conjunction with the generic security standards and the technology 
specific standards, which specifies controls applicable for particular technologies.
</para>
<para>Compliance with this standard does not negate the need for an overall security review 
of a proposed application or service. 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="Obtain a copy of the suppliers information security service descriptions" environment="ASP" pleading="mandatory" versionMaj="1" id="ASP-SECMAN-3" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The suppliers information security service descriptions should be obtained and analysed for consistency against the supplier security organisation and against your organisation&apos;s security service requirements.</policy-statement>
<checklist-question>Has the suppliers information security service claims been analysed for consistency with their organisational structure, resourcing level and your organisation&apos;s security service requirements.</checklist-question>
<howto>
<step>Obtain the suppliers information security service descriptions</step>
<step>Analyse the services in view of their stated organisational structure, their service capability claims and against your organisation&apos;s security service requirements.</step>
<step>Identify areas where the suppliers services appear to be unsupported by their structure and resourcing</step>
<step>In the context of the service to be provided analyse the impact of the disparities</step>
<step>Feed the results into your analysis of the proposed service</step>
</howto>
<risks-addressed>
<risk>Required security services may not be delivered</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that ASP contracts include a schedule detailing the security services provided and references a service level agreement for the provision of those services." environment="ASP" pleading="mandatory" versionMaj="1" id="SECMAN-11" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that ASP contracts include a schedule detailing the security services provided and references a service level agreement for the provision of those services.</policy-statement>
<checklist-question>Does the ASP contract define the security services to be provided and the service levels?</checklist-question>
<howto>
<step>Identify the security services required</step>
<step>Identify the service level required for each security service</step>
<step>Ensure that the contract for the application service provision references these services and the service level required</step>
</howto>
<risks-addressed>
<risk>The effectiveness of the service provision claims may be unsupportable</risk>
<risk>The effectiveness of the service provision claims may be unremediable through legal means</risk>
<risk>Incident management may be ineffective</risk>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Procedural security may be wholly inappropriate</risk>
<risk>Personnel security may be wholly inappropriate</risk>
<risk>Technical security may be wholly inappropriate</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Obtain a copy of the suppliers information security organisational structure" environment="ASP" pleading="mandatory" versionMaj="1" id="ASP-SECMAN-2" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The suppliers information security organisational structure must be obtained and analysed for consistency with the stated policies and claimed security services.</policy-statement>
<checklist-question>Has the suppliers information security organisational structure been analysed for consistency with the stated policies and the claimed security services.</checklist-question>
<howto>
<step>Obtain the suppliers information security organisational structure</step>
<step>Analyse the structure in view of the stated policies and security services</step>
<step>Identify areas where the suppliers defined structure appears unable to support the claimed policy objectives and the claimed security services.</step>
<step>In the context of the service to be provided analyse the impact of the disparities</step>
<step>Feed the results into your analysis of the proposed service</step>
</howto>
<risks-addressed>
<risk>A wholly inappropriate technical security solution may be implemented</risk>
<risk>A wholly inappropriate security management solution may be implemented</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Obtain a description of the suppliers arrangements for auditing the services that they provide." environment="ASP" pleading="mandatory" versionMaj="1" id="ASP-SECMAN-4" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Auditing provides independent management checks on the functioning of controls, therefore obtain a description of the suppliers arrangements for auditing the services that they provide and compare this to the regime that would be implemented were it in your own organisation.</policy-statement>
<checklist-question>Does the description of the suppliers arrangements for auditing the services that they provide equate to or exceed the level of auditing that would be provided were it performed in-house?</checklist-question>
<howto>
<step>Obtain the description of the auditing provided by the supplier</step>
<step>Ensure that the auditing to be provided equates at least to that which would be provided were the application hosted in-house</step>
</howto>
<risks-addressed>
<risk>The service may be operated in such a was as to be out of control</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that the supplier is bound by confidentiality agreements to prevent leakage of your data to other parties who may also use the ASP service." environment="ASP" pleading="mandatory" versionMaj="1" id="SECMAN-12" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that the supplier is bound by confidentiality agreements to prevent leakage of your data to other parties who may also use the ASP service.</policy-statement>
<checklist-question>Is the supplier bound by confidentiality agreements to prevent leakage of your data to other parties who might also use the ASP service.</checklist-question>
<howto>
<step>Ensure that the ASP contract includes supplier confidentiality clauses</step>
<step>Determine whether further more stringent confidentiality measures are required from the risk analysis</step>
</howto>
<risks-addressed>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Business information may be disclosed.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Obtain a copy of the suppliers information security policy" environment="ASP" pleading="mandatory" versionMaj="1" id="ASP-SECMAN-1" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The suppliers information security policy should be obtained and analysed for consistency with that of your own organisation.</policy-statement>
<checklist-question>Has the suppliers information security policy been obtained and analysed for consistency with that of your own organisation?</checklist-question>
<howto>
<step>Obtain the suppliers information security policy</step>
<step>Perform a comparative analysis between the suppliers policy and your own</step>
<step>Identify areas where the suppliers policy requirements do not meet yours</step>
<step>In the context of the service provided analyse the impact of the disparities</step>
<step>Feed the results into your analysis of the proposed service</step>
</howto>
<risks-addressed>
<risk>A wholly inappropriate technical security solution may be implemented</risk>
<risk>A wholly inappropriate security management solution may be implemented</risk>
<risk>An inappropriate security cultural solution may be implemented</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Avoid ASPs who are unwilling to disclose their security capabilities even under non-disclosure agreements" environment="ASP" pleading="mandatory" versionMaj="1" id="SECMAN-10" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Avoid using ASPs who are unwilling to disclose their security capabilities even under non-disclosure agreements</policy-statement>
<checklist-question>Is the ASP willing to provide details of their security capabilities?</checklist-question>
<howto>
<step>Determine whether the supplier is willing to disclose their security capabilities</step>
<step>Avoid those, who even under NDA will not disclose their security service capabilities</step>
</howto>
<risks-addressed>
<risk>The effectiveness of the service provision claims may be unsupportable</risk>
<risk>Incident management may be ineffective</risk>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that ASP personnel are subject to equivalent background checks as staff within your own organisation" environment="ASP" pleading="mandatory" versionMaj="1" id="SECMAN-13" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that ASP personnel who will be working on the ASP solution are subject to equivalent background checks as staff within your own organisation</policy-statement>
<checklist-question>Are ASP personnel working on the ASP solution subject to equivalent background checks as staff within your own organisation?</checklist-question>
<howto>
<step>Determine what background checks are performed by the ASP</step>
<step>Compare these checks to those performed by your own organisation</step>
<step>Determine whether there are any major mismatches and thus, exposures.</step>
</howto>
<risks-addressed>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Technical security controls may be undermined</risk>
<risk>Procedural security controls may be undermined</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that hardening of the components of the solution takes place in line with the policies and standards that are applicable within your organisation." environment="ASP" pleading="mandatory" versionMaj="1" id="SECMAN-16" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that hardening of the components of the solution takes place in line with the policies and standards that are applicable within your organisation.</policy-statement>
<checklist-question>Is it ensured that hardening of the components of the solution takes place in line with the policies and standards that are applicable within your organisation?</checklist-question>
<howto>
<step>Obtain details of the component hardening that the ASP performs</step>
<step>Compare the hardening process used against the steps that your organisation would take.</step>
<step>Identify any substantive differences that would reduce the security of the solution when compared to hosting it by your own organisation</step>
</howto>
<risks-addressed>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Technical security controls may be undermined</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that a regime of measuring the security services provided are in place and the ASP provides these at an agreed frequency" environment="ASP" pleading="mandatory" versionMaj="1" id="SECMAN-9" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that a regime of measuring the security services provided are in place and the ASP provides these at an agreed frequency</policy-statement>
<checklist-question>Is there a regime for measuring the security services provided at an appropriate frequency?</checklist-question>
<howto>
<step>For each of the security services provided as part of the ASP define measures of effectiveness</step>
<step>For each of the measures of effectiveness determine the frequency of report to be provided by the ASP.</step>
</howto>
<risks-addressed>
<risk>The effectiveness of the service provision claims may be unmeasured</risk>
<risk>Incident management may be ineffective</risk>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that ASP contracts of employment place equivalent or greater emphasis on information security as that in your organisation&apos;s own contracts of employment" environment="ASP" pleading="mandatory" versionMaj="1" id="SECMAN-14" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that ASP contracts of employment place equivalent or greater emphasis on information security as that in your organisation&apos;s own contracts of employment</policy-statement>
<checklist-question>Do the ASP contracts of employment place equivalent or greater emphasis on information security as that in your organisation&apos;s own contracts of employment?</checklist-question>
<howto>
<step>Determine the information security clauses within your organisation&apos;s contract of employment</step>
<step>Determine the information security clauses within the ASP contracts of employment</step>
<step>Determine whether any mismatches are significant</step>
</howto>
<risks-addressed>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Technical security controls may be undermined</risk>
<risk>Procedural security controls may be undermined</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that the ASP management practices in relation to the components that make up the solution do not introduce vulnerabilities" environment="ASP" pleading="mandatory" versionMaj="1" id="SECMAN-15" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that the ASP management practices in relation to the components that make up the solution, do not introduce vulnerabilities</policy-statement>
<checklist-question>Has it been ensured that the ASP management practices in relation to the components that make up the solution do not introduce vulnerabilities?</checklist-question>
<howto>
<step>Obtain the management procedures for the solution components from the ASP</step>
<step>Compare these management procedures to those that would be applied were the solution hosted by your own organisation</step>
<step>Identify substantive differences that may give rise to security vulnerabilities</step>
</howto>
<risks-addressed>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Technical security controls may be undermined</risk>
<risk>Procedural security controls may be undermined</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that the ASP has a well defined audit capability" environment="ASP" pleading="mandatory" versionMaj="1" id="SECMAN-8" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that the ASP undertakes periodic audits</policy-statement>
<checklist-question>Is the ASP subject to periodic audits?</checklist-question>
<howto>
<step>Obtain a description of the audit cycle for the service</step>
<step>If one does not exist or if the cycle is too long this should be considered a deficiency</step>
</howto>
<risks-addressed>
<risk>The effectiveness of the service provision claims may be unmeasured</risk>
<risk>Incident management may be ineffective</risk>
<risk>Security responsibilities may be confused</risk>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure that the supplier provides contact names and details for each element of their security organisation that will deliver security services to your organisation." environment="ASP" pleading="mandatory" versionMaj="1" id="ASP-SECMAN-5" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>It must be ensured that the supplier provides contact names and details for each element of their security organisation that will deliver security services.</policy-statement>
<checklist-question>Has the supplier provided contact names and details for each element of the security organisation that is to deliver security services to your organisation?</checklist-question>
<howto>
<step>Using the supplier organisation chart and the security services that are to be supplied ensure that all contact details have been supplied.</step>
<step>Ensure that the number of services to be provided by each individual named are reasonable</step>
<step>Ensure that the contact info is maintained in an appropriate form such that incidents and responses can be appropriately dealt with.</step>
</howto>
<risks-addressed>
<risk>The service provision claims may unsupportable</risk>
<risk>Incident management may be unfeasible</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure the ASP has a well defined information security organisation with clearly defined responsibilities" environment="ASP" pleading="mandatory" versionMaj="1" id="SECMAN-7" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Security Compliance:Security Management" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure the ASP has a well defined information security organisation with clearly defined responsibilities</policy-statement>
<checklist-question>Does the ASP have a well defined information security organisation with clearly defined responsibilities?</checklist-question>
<howto>
<step>Obtain the information security organisation from the ASP</step>
<step>Correlate the security services provided with the security organisation</step>
<step>Identify any significant mismatches</step>
<step>Correlate the security services provided against the security services required</step>
<step>Identify any significant mismatches</step>
</howto>
<risks-addressed>
<risk>The service provision claims may be unsupportable</risk>
<risk>Incident management may be unfeasible</risk>
<risk>Security responsibilities may be confused</risk>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</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>
<control level="above baseline" techversion="Any" title="Vulnerability scanning/penetration testing should be performed prior to any new service going live" environment="ASP" pleading="recommended" versionMaj="1" id="NETSEC-1" availability-level="above baseline" disclosure-level="above baseline" technology="Any" versionMin="0" section="Network Security Configuration:Internet Considerations" integrity-level="above baseline" dp-level="above baseline" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Where the new service is to be host by an ASP vulnerability scanning/penetration testing should be performed prior to the new service going live</policy-statement>
<checklist-question>Will vulnerability scanning/penetration testing be performed prior to the new service going live?</checklist-question>
<howto>
<step>Identify whether the ASP provides any monitoring of the platform builds</step>
</howto>
<risks-addressed>
<risk>Security vulnerabilities may go undetected and lead to site compromise</risk>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Technical security controls may be undermined</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="The new service should be protected by a firewall" environment="ASP" pleading="recommended" versionMaj="1" id="NETSEC-2" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Network Security Configuration:Internet Considerations" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The new ASP hosted service should be protected by a firewall</policy-statement>
<checklist-question>Is the new ASP hosted service protected by a firewall?</checklist-question>
<howto>
<step>Identify whether the ASP can supply the service with firewall protection in place</step>
</howto>
<risks-addressed>
<risk>Security vulnerabilities associated with non-essential services may lead to compromise of the system</risk>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Technical security controls may be undermined</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</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>
<control level="above baseline" techversion="Any" title="Intrusion detection should be deployed" environment="ASP" pleading="recommended" versionMaj="1" id="SECMON-1" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Auditing and Monitoring:Events to be alerted in real-time" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Intrusion detection systems should be deployed in order to identify attacks against the service</policy-statement>
<checklist-question>Has an intrusion detection system been deployed in order to identify attacks?</checklist-question>
<howto>
<step>Determine from the risk analysis of the system it&apos;s importance</step>
<step>For important systems deploy an intrusion detection solution to monitor for attempted breaches</step>
</howto>
<risks-addressed>
<risk>Attempts to breach the system may go undetected.</risk>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Technical security controls may be undermined</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlsection>
<controlsection><title>Audit log destination and format</title>
</controlsection>
<controlsection><title>Events to be audited</title>
<control level="baseline" techversion="Any" title="Monitoring of the platforms of the ASP components should take place to flag when any components move out of alignment with the hardened build specification." environment="ASP" pleading="recommended" versionMaj="1" id="SECMON-`2" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Auditing and Monitoring:Events to be audited" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Monitoring of the platforms of the ASP components should take place to flag when any components move out of alignment with the hardened build specification.</policy-statement>
<checklist-question>Will the solution provide perform monitoring of the platforms of the ASP components to flag when any components move out of alignment with the hardened build specification?</checklist-question>
<howto>
<step>Identify whether the ASP provides any monitoring of the platform builds</step>
</howto>
<risks-addressed>
<risk>Security breaches of the platforms may go undetected</risk>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Technical security controls may be undermined</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="The ASP should provide monitoring of the firewall rule base" environment="ASP" pleading="recommended" versionMaj="1" id="SECMON-3" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Auditing and Monitoring:Events to be audited" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The ASP should provide monitoring of the firewall rule base</policy-statement>
<checklist-question>Does the ASP provide monitoring of the firewall rule base?</checklist-question>
<howto>
<step>Identify whether the ASP can monitor firewall rule changes and reconcile the changes to valid, authorised changes.</step>
</howto>
<risks-addressed>
<risk>Unregulated rule changes may introduce security vulnerabilities that may lead to compromise of the system</risk>
<risk>Legal and regulatory responsibilities may not be met</risk>
<risk>Technical security controls may be undermined</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlsection>
</controlchapter>
<controlchapter><title>Other</title>
<control level="baseline" techversion="Any" title="Ensure that the Application Service Provider and your organisation develop and agree incident handling processes and procedures" environment="ASP" pleading="mandatory" versionMaj="1" id="OTHER-2" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that the Application Service Provider and your organisation develop and agree incident handling processes and procedures</policy-statement>
<checklist-question>Have incident handling processes and procedures been developed and agreed with the Application Service Provider?</checklist-question>
<howto>
<step>Define security incidents that require a response</step>
<step>Determine the responses to be taken in the event of a security incident</step>
<step>Determine the party responsible for taking the response</step>
<step>Capture the above in a process document</step>
<step>Define procedures to be followed to execute the process</step>
<step>Implement the process and procedures between your organisation and the ASP.</step>
</howto>
<risks-addressed>
<risk>Remedial action may fail to be taken in the event of an incident</risk>
<risk>Inappropriate and potentially more damaging action may be taken in the event of an incident</risk>
<risk>Legal, regulatory or contractual obligations may be breached</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="above baseline" techversion="Any" title="Ensure that for a high availability requirement service that a fault tolerant implementation is deployed" environment="ASP" pleading="mandatory" versionMaj="1" id="OTHER-1" availability-level="above baseline" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Ensure that for a high availability requirement service that a fault tolerant implementation is deployed</policy-statement>
<checklist-question>Has a fault tolerant implementation been deployed?</checklist-question>
<howto>
<step>Ensure that the service is deployed with RAID, fault tolerant power supplies, online backups, mirroring, diverse network connections</step>
</howto>
<risks-addressed>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Ensure a risk analysis is performed on the service to be provided" environment="ASP" pleading="mandatory" versionMaj="1" id="ASP-OTHER-1" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>A risk analysis must be performed on the service to be hosted to ensure that appropriate controls are built into the solution</policy-statement>
<checklist-question>Has a risk analysis been performed on the service to be hosted?</checklist-question>
<howto>
<step>Perform a risk analysis on the application to determine the control requirements</step>
</howto>
<risks-addressed>
<risk>A wholly inappropriate security solution may be implemented</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="The security provided by the service provider must equate to the same or greater level of security that would be put in place were you to host it using your own organisation&apos;s capabilities." environment="ASP" pleading="mandatory" versionMaj="1" id="ASP-OTHER-2" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>The security provided by the service provider should equate to a same or greater level of security that would be put in place were you to host it by your own organisation.</policy-statement>
<checklist-question>Is the security provided by the service provider equivalent or greater than the level of security that would be put in place were it hosted by your own organisation?</checklist-question>
<howto>
<step>Determine the appropriate level of security control required using risk analysis</step>
<step>Determine the security capability of the provider</step>
<step>Determine whether this delivers the control required against the risk analysis</step>
<step>Determine whether this delivers the same control as that were you to host the service yourselves.</step>
</howto>
<risks-addressed>
<risk>The security solution delivered may be wholly inappropriate for the service</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
<control level="baseline" techversion="Any" title="Incident handling processes and procedures should be tested" environment="ASP" pleading="recommended" versionMaj="1" id="OTHER-3" availability-level="Any" disclosure-level="Any" technology="Any" versionMin="0" section="Other" integrity-level="Any" dp-level="Any" safety-level="Any">
<revhistory>
</revhistory>
<policy-statement>Incident handling processes and procedures should be tested</policy-statement>
<checklist-question>Have incident handling processes and procedures been tested?</checklist-question>
<howto>
<step>Define and agree scenarios to be tested with the ASP</step>
<step>Simulate the scenario and execute the incident handling procedure</step>
<step>Measure deficiencies with the plan and its execution and re-develop the process and procedure accordingly</step>
</howto>
<risks-addressed>
<risk>Remedial action may fail to be effective in the event of an incident</risk>
<risk>Inappropriate and potentially more damaging action may be taken in the event of an incident</risk>
<risk>Legal, regulatory or contractual obligations may be breached</risk>
<risk>Business information may be accidentally or maliciously altered.</risk>
<risk>Business information may be disclosed.</risk>
<risk>Business information and applications may be unavailable.</risk>
</risks-addressed>
</control>
</controlchapter>
</standard>

