CoCo V4 When, What, How?

May 14th, 2010 by Ian Tinney

 

Are you concerned about the new CoCo V4.1 standard? Possibly asking questions like, "What are the new requirements?", "When do I need to be compliant?" or "How do I achieve compliance?". Then please Read on....

 

What?

What's new in CoCo V4.1?

Well essentially the following topics are the main focus of CoCo V4.1.

• Mobile working - full implementation of compliant service

• Firewall specification (EAL 4)

• Execution of unauthorised software

• Requirement for IT Healthchecks (CHECK / CREST)

• Labelling e-mails with protective markings

When?

From 1 November 2009 CoCo version 4.1 should be used for all new authorisation and re-authorisation applications.

A transition period of up to six months will apply, during which non-compliance against new or upgraded CoCo version 4.1 controls will be regarded as acceptable, provided that the level of compliance demonstrated is at least good enough to satisfy CoCo version 3.2 requirements.

 

From 1 May 2010 compliance needs to be achieved against CoCo version 4.1 controls. Exceptionally, compliance against individual controls can be interpreted as a firm plan to introduce appropriate measures within a reasonable timeframe, depending on the overall level of compliance demonstrated by the authorisation (or re- authorisation) submission in the round.

 

How?

Using "EQALIS Splunk for CoCo" application of course!

Please see our applications page to see how EQALIS can provide your CoCo V4.1 solution.

 

EQALISADVISOR

 

Tags: Compliance, Coco, Blog, Non Compliance, Splunk, Eqalis

Posted in Splunk | 0 Comments