<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>BS25999.COM &#187; Compliance</title>
	<atom:link href="http://www.bs25999.com/tag/compliance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bs25999.com</link>
	<description></description>
	<lastBuildDate>Tue, 13 Jul 2010 12:39:23 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Achieving BS25999 Certification</title>
		<link>http://www.bs25999.com/2009/12/achieving-bs25999-certification/</link>
		<comments>http://www.bs25999.com/2009/12/achieving-bs25999-certification/#comments</comments>
		<pubDate>Tue, 22 Dec 2009 22:22:12 +0000</pubDate>
		<dc:creator>harveyf</dc:creator>
				<category><![CDATA[BS25999]]></category>
		<category><![CDATA[Audit]]></category>
		<category><![CDATA[Certification]]></category>
		<category><![CDATA[Compliance]]></category>

		<guid isPermaLink="false">http://www.bs25999.com/?p=44</guid>
		<description><![CDATA[BS25999 Part 2 is a Specification, not a Code of Practice like Part 1. So what is the difference? Part 2 is a Specification and deals with ‘Shall’ rather than ‘Should’ as the Part 1 Code of Practice does. Titled BS 25999–2:2007 Specification for business continuity management and includes… * Documentation Requirements * Management responsibility [...]]]></description>
			<content:encoded><![CDATA[<p>BS25999 Part 2 is a Specification, not a Code of Practice like Part 1. So what is the difference? Part 2 is a Specification and deals with ‘Shall’ rather than ‘Should’ as the Part 1 Code of Practice does.</p>
<p>Titled BS 25999–2:2007 Specification for business continuity management and includes…</p>
<p>* Documentation Requirements<br />
* Management responsibility<br />
* Internal BCMS Audit<br />
* Management review of BCMS<br />
* BCMS Improvement</p>
<p>The standard was published on November 20th 2007</p>
<p><em>How does an organisation seek compliance with the standard?</em></p>
<p>As with most management standards the process will be relatively standardised using the guidelines in ISO 17021</p>
<h3>STEP 1 — Application</h3>
<p>Apply to a certification body, certification bodies are organisations that are accredited to certify organisations, for example BSI or LRQA (although these two examples are not the only ones). An understanding of the scope of the BCMS will need to be made. The certification body will then create a proposal detailing the number of assessment days required and costs etc. If the organisation chooses to proceed the assessment should take place.</p>
<h3>STEP 2 — Pre Assessment</h3>
<p>A pre assessment may be used to provide a snap shot of readiness for the full assessment. Sampling and other techniques may be used in this pre assessment. Any areas of omission will be raised and an assessment of remedial work, should any be needed, would be made. The formal assessment may be delayed if it is thought that it would be unlikely that the organisation would pass.</p>
<h3>STEP 3 — Assessment</h3>
<p>The formal assessment is then made during which all areas of the Part 2 Specification will be covered. In line with ISO17021 and in a similar way to other management standards the formal assessment is done in two parts.</p>
<p><strong>Stage 1:</strong> This stage will cover the Business Continuity Management System and will examine BCMS documentation, the management review/audit system and evaluation of readiness for stage 2. Planning for Stage 2 will also take place.</p>
<p><strong>Stage 2:</strong> This stage examines the implementation of the BCMS i.e. objective evidence. It may involve inspection of records, interviews of personnel and physical inspections.</p>
<p>Any observations or non conformities will be formally recorded and a recommendation for certification or not made.</p>
<h3>STEP 4 - Recommendation and Award</h3>
<p>If client achieves recommendation for certification body this recommendation will be forwarded to the BS25999 Certification Manager for final review and issuing of certificates. If the client fails the audit a corrective action plan is usually agreed and a second audit arranged.</p>
<h3>STEP 5 — Continued Assessment</h3>
<p>When the certificate has been awarded surveillance audits will be planned, typically at yearly intervals. These surveillance visits will examine the effectiveness of the BCMS, management reviews/audit, progress of continual improvement actions, change review and possibly the use of the registration marks in publicity materials etc. A full reassessment will also be carried out at longer intervals, usually 3 years although this will depend on both the organisation and the certification body.</p>
<p>What are the benefits of certification?</p>
<p>As I have mentioned the standard comes in two parts. Splitting them is designed to make it easier to understand and deploy. Part 2 or the Specification sets out the minimum that an organisation should do in order that its business continuity systems are effective.</p>
<p>Implementing BS25999 Part 1 or the Code Practice will undoubtedly provide many benefits to an organisation but there is no doubt that achieving certification will require significant extra work, so what are the benefits?</p>
<p>In a word, demonstrability.</p>
<p>Having certification to a known and accepted management standard such as BS25999 Part 2 avoid saying to stakeholders ‘Trust Me’</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bs25999.com/2009/12/achieving-bs25999-certification/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Compliance — Overhead or Business Benefit?</title>
		<link>http://www.bs25999.com/2009/12/compliance-overhead-or-business-benefit/</link>
		<comments>http://www.bs25999.com/2009/12/compliance-overhead-or-business-benefit/#comments</comments>
		<pubDate>Mon, 21 Dec 2009 23:30:15 +0000</pubDate>
		<dc:creator>harveyf</dc:creator>
				<category><![CDATA[BCM]]></category>
		<category><![CDATA[Compliance]]></category>

		<guid isPermaLink="false">http://www.bs25999.com/?p=18</guid>
		<description><![CDATA[The very word “Compliance” strikes dread in many senior management forums. Viewed most often as a pain, necessary evil, or at best a burden on the business, Compliance has become a word most often associated with a sigh of despair. But should this really be the case? The very reason many senior managers have to [...]]]></description>
			<content:encoded><![CDATA[<p>The very word “Compliance” strikes dread in many senior management forums.</p>
<p>Viewed most often as a pain, necessary evil, or at best a burden on the business, Compliance has become a word most often associated with a sigh of despair. But should this really be the case? The very reason many senior managers have to be dragged kicking and screaming into the Compliance arena is often the complexity of the subject and fear of the unknown.</p>
<p>At the end of the day most senior managers are focused on making money for the business, controlling costs and generating value for the shareholders so they view compliance issues as a distraction.</p>
<p>Now that is interesting in itself, particularly the latter two points.</p>
<p>Surely controlling costs and generating value for the shareholders should be really good drivers to understand what Compliance can mean to the business? Part of the problem, and the perception, is the plethora of different compliance issues that appear when the surface of the topic is scratched, e.g. Human Rights, Privacy, Data Protection, Freedom of Information, Taxation, Corporate Governance, Intellectual Property/Copyright, Health &amp; Safety, Fraud &amp; Corruption, Competitive Practice, Anti-trust, Money Laundering, Standards (e.g. ISO/IEC27001, COBIT, SAS70) and much more.</p>
<p>Is it any wonder why senior management would rather avoid getting embroiled in this as much as possible? The problem is — it is their responsibility, and they are accountable for Compliance so, in time, many will become to realise that they have no choice and even that Compliance can provide real benefits to the business.</p>
<h3>How can this ever happen?</h3>
<p>Surely the whole Compliance effort costs a fortune and bogs the business down in unnecessary procedure?</p>
<p>All many managers see is increasing red-tape, extra costs for controls, new or increasing compliance teams, personal liability and spiraling overheads.</p>
<p>But, is this a fair view? Sure there are additional costs to be carried for the compliance efforts, but it could be argued that these are more than balanced by factors such as:</p>
<p>* Increased Customer/Shareholder/Partner confidence and trust<br />
* Improved analysis, documentation and efficiency of business processes<br />
* Better business resilience<br />
* Greater buy-in from management and staff<br />
* The de-duplication of control efforts<br />
* Faster audits with less hold points<br />
* Reduced audit costs Reduced crisis/incident management and remedial action costs<br />
* Avoidance of legal or regulatory sanctions or fines and more …</p>
<p>It is surprising how the very attempt to ensure Compliance can often become a catalyst for change. As a business grows often the development and documentation of sound business processes falls by the wayside and greater reliance is placed upon staff knowledge and expertise.</p>
<p>This can work for a while but we live in an ever changing world where the pace of life is increasing daily and a lack of sound business practice will mean trouble in the future. It only takes a key member of staff to leave, or say a disgruntled member of staff to ‘throw a spanner in the works’ and serious repercussions can ripple throughout the business.</p>
<p>Yes — we all know we should write procedures so that someone can take over if the worst should happen; but the ‘instant’ nature of the working environment today (e.g. the Internet, email, instant messaging, mobile connectivity) makes that very unlikely — we just do what we do!</p>
<p>This is where Compliance brings back some sanity to the workplace. An auditor is not satisfied by ‘hearsay’ evidence that a key business process is operating in line with legal or regulatory requirements — they want cold, hard documentary evidence!</p>
<p>The Compliance drive has a tendency therefore to underline the need for key controls, procedures and evidence, and to ensure that adequate funding is committed to their maintenance. What is often missed is the opportunity to develop one management system to control all aspects of compliance, regardless of law, regulation or standard.</p>
<p>Many organisation still approach Compliance from a piecemeal angle — HR do their bit, IT do their bit, Legal do their bit, etc. It is also common to see organisations creating separate teams, tasked with compliance to a particular piece of legislation. This is, at best, unwieldy, inefficient and expensive; a practice to be avoided. This can be due to the ‘siloed’ nature of many organisations, internal politics, expertise issues, or just plain stubbornness to get involved.</p>
<p>The problem is Compliance issues usually cut right across the business and a very strong lead is needed for any team that is going to co-ordinate all issues company wide. A competent Compliance team can build one management system that will provide co-ordination of the compliance effort, one repository and source of information for audit trails and associated evidence.</p>
<p>This avoids the ‘empire building’ that often happens when say a new piece of legislation comes along, containing and potentially reducing costs.</p>
<h3>So, ‘Overhead or Business Benefit’?</h3>
<p>Much depends on your viewpoint and the type of organisation you work for. Finance, Banking and Insurance are heavily regulated, and accept Compliance as just part of daily business, whereas for, say a manufacturing business, this is all just a cost they would prefer not to have.</p>
<p>Hopefully this will change in time, legislation may become simpler and easier to understand (eh .. possibly..), business practices and management systems will improve, and many will see how the Compliance effort can bring real dividends.Business</p>
<h6>Clifford May, Consultancy Practice, Integralis Ltd UK</h6>
]]></content:encoded>
			<wfw:commentRss>http://www.bs25999.com/2009/12/compliance-overhead-or-business-benefit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
