Source ISO Ref. Requirement Testing Procedures v1.1 Clause v2.1.1 Clause
Source ISO Ref. Requirement Testing Procedures v1.1 Clause v2.1.1 Clause
Source ISO Ref. Requirement Testing Procedures v1.1 Clause v2.1.1 Clause
1 Significanc Control
Scope Source ISO Ref. Requirement Testing Procedures
Clause Clause e Objective/Control
The scope should be made available to the auditor and should cover the
A communications provider must be able to demonstrate a clear interconnect types (as per the standard), the protocols used by the CP to support
understanding of where and how the standard applies to their
n/a 4.1 High. All ND1643 n/a Documented scope these, the product or service names the CP associates with these interconnects
organisation (and contractors or 3rd parties), meeting the
and the locations affected.
requirements of the Scopesection.
The auditor should validate that the scope is sufficiently clear to clearly identify
The scope must enable the auditor and others to clearly identify which personnel, equipment, physical locations, secure perimeters and so on are
n/a 4.1 High. All ND1643 n/a Documented scope which personnel, equipment, physical locations, secure perimeters
in scope, and which are not.
and so on are in scope.
1. Auditors should review the relevant security policy document(s) and ensure it
The policy should explain how your organisation implements the
covers the controls within the Standard and explains how the CP implements
4.1 4.2 ISO27002 A.5.1.1 Information security controls that are required by the minimum standard. We
Medium All and measures the controls.
policy document recommend it explains how you measure the effectiveness of the
controls. 2. The auditor should ensure that the document is available to those who require
it, and that they know where it is.
Management The auditor’s assumption should be that this is a ‘pass’ as a CP would not seek
5.1 4.3 ISO27002 A.6.1.1 • Ensure appropriate funding and resource is available to
Medium All commitment to certification without appropriate funding being in place, unless evidence comes
information security implement the standard’s controls; to the contrary comes to light during the audit
The auditor should validate that the responsibility for implementation and
Management compliance of the controls is clearly assigned within the organisation and that
5.1 4.3 Medium All ISO27002 A.6.1.1 commitment to
• Assign key roles and responsibilities for implementation, this is supported by the appropriate organisation charts. Job Descriptions, Notes
information security operation, monitoring and improvement of the controls;
of 1 to 1 reviews etc.
Management • Set the strategic approach the organisation will take to achieve The Information Security Document and Management Commitment to
5.1 4.3 Medium All ISO27002 A.6.1.1 commitment to compliance, and articulate this through policy documents and information security (Sections 4.2. and 4.3 above) meet this requirement. No
information security planning; further validation is expected of the auditor.
The auditor should validate that employees within scope have been made aware
of their responsibilities through review of training material, team briefing
Management • Ensure those employees within the scope of Interconnects are material, formal communications, email circulation lists etc. Auditors could also
5.1 4.3 Medium All ISO27002 A.6.1.1 commitment to
information security aware of their responsibilities through training and awareness. check the training records of personnel in scope where a company formally
records such activity.
A list of third party suppliers or other external parties involved must be shown
5.2 4.4 High. All ISO27002 A.6.2.3 Third Party Agreements
to the auditor. The auditor should verify this list by looking at access logs to sites,
and interviewing staff within scope.
A communications provider may contract a third-party to 1. CPs should demonstrate to the auditor that any new or renegotiated contracts
implement some of the controls in this document. The contract meet the control by:
with the third party must clearly cover the relevant security a) Clearly covering the relevant security controls, and include the right for the CP
requirements, and must also cover the right to audit. to audit the supplier.
b) Stipulating that obligations must be passed on to companies and individuals
The third party may choose to get external certification to further down the supply chain, as appropriate for compliance with the standard
5.2 4.4 High. All ISO27002 A.6.2.3 Third Party Agreements demonstrate their compliance with the contracted controls. 2. It is the CPs intention to request new Suppliers or new contract awards meet
the requirements of MSS and that a process exists to support this
3. The CP should demonstrate that a process is in place to review, evaluate and
accept the impact when a Supplier refuses to support the controls within the
Standard either as a result if the “market power” of the Supplier or where the
commercial implications are unreasonable. The inspection should validate that
this process has been used where appropriate.
1. The auditor should look for evidence that the CP monitors and enforces the
requirements on those Suppliers contracted to meet the controls within the
The communications provider must monitor the enforcement of the
5.2 4.4 High. All ISO27002 A.6.2.3 Third Party Agreements requirements. This monitoring is typically performed through Standard.
2. Ad-hoc checks by the auditor on any third parties encountered during an audit
logging and auditing procedures.
are encouraged but are not mandatory.
The communications provider must seek and maintain assurances 1. The auditor should look for evidence that the CP is actively seeking and
from the third party that the required security behaviours have maintaining such assurances, perhaps in minutes of supplier review meetings,
been communicated to their personnel and are being followed. induction briefings, audits or other mechanisms
5.2 4.4 High. All ISO27002 A.6.2.3 Third Party Agreements
Obligations must be passed on by any third-parties, as appropriate 2. Ad-hoc checks by the auditor on any third parties encountered during an audit
for compliance with the standard, to companies and individuals are encouraged but are not mandatory
further down the supply chain.
1. The auditor should review the CP’s documentation for evidence of clearly
defined roles and responsibilities, confirm that these roles and responsibilities
Roles and
6.1 4.5 Medium All ISO27002 A.8.1.1 responsibilities exist either within the organisation or are contracted with a 3rd party and that
individuals within scope have an adequate understanding of them.
Communications providers must be able to show that security roles
and responsibilities are defined and documented in the policy
documentation.
1. Where roles and responsibilities are contracted outside the organisation the
Roles and
6.1 4.5 Medium All ISO27002 A.8.1.1 responsibilities auditor should check that there evidence that the CP is actively managing these.
If the pre employment checks produce any anomalies or causes for concern, then
If the checks produce any anomalies or causes for concern then
either senior management within the CP are expected to be involved in the
senior management must be involved in the consideration of the consideration of the employment of the individual in question or senior
6.2 4.6 Medium All ISO27002 A.8.1.2 Screening employment of the individual in question and if they remain in
management must have agreed the process that shall be used to authorise such
employment with the organisation then records of the
exceptions. The auditor should validate that such a process exists and is being
consideration should be kept. used.
Communications providers must be able to demonstrate that the 1. The auditor should review a sample of two employment contracts for
6.3 4.7 Medium All ISO27002 A.8.1.3 Terms and Conditions of terms and conditions of the employment contract for all employees, employees within scope and check that they include an appropriate general
Employment contractors and third party users within scope state their and the statement which adequately supports this control.
organization’s responsibilities for information security. 2. The auditor should also check that the contracts checked are signed.
Auditors should review the process for leavers and ensure managers, HR or both
are aware of it. Auditors should either:
• Review list of individuals (and or roles) with access to a piece of equipment
within scope. Identify when this was last updated and whether this is
appropriate to the rate of employee turnover , then ensure that all listed
individuals are still in employment and remain within the defined scope. If
shared accounts are used instead of individual accounts, identify the date of last
leaver, ensure that passwords have been changed since (both internally and with
6.5 4.8 High. NGN ISO27002 A.8.3.3 Removal of Access an interconnect partner, if appropriate) .
Rights The auditor should also validate that for a leaver within scope that any
computers, access tokens, keys etc which were allocated to the leaver were
recovered.
• Request that the CP demonstrate via a specific leaver (chosen by the auditor) ,
how leavers can no longer attempt to gain access to interconnect equipment, for
example by preventing access to buildings and barring remote access to the
network, cancelling of passwords etc. The CP should also demonstrate that any
The access rights of all employees, contractors and third party users computers, access tokens, keys etc which were allocated to the leaver were
to systems within scope must be removed upon termination of their recovered.
employment, contract or agreement, or adjusted if their role
changes.
Ensuring appropriate asset recovery (computers, access tokens,
keys etc) and account closures follow employment terminations.
2. The access rights of third party users to systems within scope must be
removed upon termination of their employment with the 3rd party, or of the
contract or agreement between the CP and 3rd party, or adjusted if their role
changes within the 3rd party. The auditor should look for evidence that the CP
Removal of Access
6.5 4.8 High. NGN ISO27002 A.8.3.3 Rights has covered the responsibilities within its contract with the 3rd party and is
actively managing and vetting these, perhaps in minutes of supplier review
meetings, induction briefings, audits or other mechanisms. The auditor is not
expected to undertake physical audits of any such 3rd party not collocated with
the CP.
3. Where 3rd party supply contracts have been reassigned, the auditor should
6.5 4.8 High. NGN ISO27002 A.8.3.3 Removal of Access ask the CP to demonstrate that the previous organisation and its employees have
Rights had their access rights removed. The auditor is not expected to undertake
physical audits of any such 3rd party not collocated with the CP.
It is also recommended that communications providers operate a Whilst not a pass /fail criteria the Auditor should note whether such reviews are
Removal of Access policy of regular internal review of access. Where access is granted undertaken. This may provide additional evidence towards whether the assessor
6.5 4.8 Advice NGN ISO27002 A.8.3.3 Rights to an interconnected providers equipment this should also be done views that there is adequate management commitment to information security
in partnership with the interconnected provider. ( see above)
1. The auditor should check that individuals who have access to a CP’s secure
areas and also shared( 3rd party) areas have been made aware of and comply
Communications providers must have robust processes/policies in
with the relevant security procedures. This can be demonstrated through
place to ensure that:
7.1 4.9 Medium All ISO27002 A.9.1.1 Physical Security
• Employees display the appropriate photo ID cards, when required training materials, notes of team meetings, copies of email briefings etc. The
Perimeter auditor should be sensitive to the size of the CP being audited.
to by their organisation or the host’s security policy.
2. Whilst not mandatory the auditor, where possible, encouraged to verify the
• Employees remain within authorised areas within sites.
understanding and compliance of any individuals encountered during the
inspection of interconnect locations.
1. The auditor should assess whether the controls are effective both for a CPs
own locations and any 3rd party locations by validating that access requires the
use of entry controls and that these can only be obtained by authorised
You must lock or otherwise physically restrict access to areas
7.2 4.10 ISO27002 A.9.1.2 personnel who meet the controls set out within the Standard. This should apply
High. All Physical entry controls containing interconnect equipment to authorised individuals who
are in scope of this standard. to any individual entering such areas, not just those employed directly or
indirectly by the CP.
2. The auditor should also check that any personnel spoken to during the physical
audits agree the controls are effective.
1. The auditor should review the list of people authorised to access a CPs secure
areas unescorted and how the CP manages/validates this to ensure that these
people meet the requirements of this standard.
2. The auditor should validate a process exists such that where an individual who
A process must be in place for granting and removing access, is not authorised yet requires legitimate access to a secure area can be
7.2 4.10 High. All ISO27002 A.9.1.2 Physical entry controls whether the perimeter is controlled by your organisation or a third- appropriately escorted and supervised.
party. 3. Whilst it will not be possible for the auditor to view a similar list for 3rd party
sites, the auditor should view the information provided by the 3rd party host
covering physical entry procedures and the contract between the CP and the 3rd
party. The latter should adequately cover the host’s obligations to extend the
Standard’s requirements to other CPs within the shared area.
1. Where a CP is acting as the host and in its own secure areas, the auditor should
validate that appropriate maintenance routines are documented, have been
scheduled, undertaken and the results recorded.
Equipment in shared areas (the whole room, not just the cage or 2. Where issues have been identified with this environmental equipment
7.3 4.11 Medium NGN, ISO27002 A.9.2.4 (Environmental) rack) must be correctly maintained to ensure that it has no adverse appropriate and timely action to rectify faults should be demonstrated to the
Internet Equipment Maintenance impact on the environment containing other communications auditor. As an example a non functioning fire alarm once detected should be
providers’ equipment. addressed as a matter of urgency whereas instances of over temperature alarms
being triggered in the midst of a heat wave might be deemed less critical or
transient.
1. The auditor should validate that the responsibility of the sharer is clearly
Owners of shared areas are responsible for setting and enforcing
stated within any contract between the host and its users of the shared space by
minimum equipment standards to reduce the chance of electrical
NGN, and fire safety incidents. checking the CPs own contract with the host.
(Environmental)
7.3 4.11 Medium ISO27002 A.9.2.4 2. The auditor should also check that the contract mandates that the hosting
Internet Equipment Maintenance Without this control catastrophic equipment failure (for example a
provider will enforce the same equipment safety standards on all other tenants
fire or electrical fault) in a shared area may adversely influence the
facility and other users. 3. This contract between the host and sharing CPs should also cover the
environmental conditions/services being provided by the host.
A change control process must exist. It must cover changes to the The auditor should validate that a change control process exists covering the
8.2 4.13 Medium All ISO27002 A.10.1.2 Change Management equipment within scope, and include: authorisation for changes, equipment in scope and at least authorisation for changes, the review of planned
review of planned changes and maintaining a log of changes. changes and maintaining a log of changes
If equipment cannot automatically log user activity then the change Where equipment cannot log, then the auditor should check that a change
8.4 4.15 Medium All. ISO27002 A.10.10.1 Audit logging management process must be used instead or to supplement the management process exists to record who logged on, when and for what purpose
required information (see above). and that records are retained for the appropriate period of time.
System administrator and system operator activities should be
logged. 1. The auditor should check that administrator and system operator activities are
Communications providers must be able to log and subsequently logged and record a full history of administrator activities on the equipment in
show full history of system administrator and system operator scope, including both successful and failed authentication attempts,
Administrator and
8.5 4.16 Medium All ISO27002 A.10.10.4 operator logs activities on equipment that’s scope including both successful and configuration, management and operational changes.
failed authentication attempts. Configuration, management and 2. The auditor should request that the CP demonstrate a log entry from as close
operational changes to the interconnect equipment should be as is practical to the 90 day limit
logged where possible.
Logs must be retained for 90 days.
If equipment cannot automatically log user activity then the change Where equipment within scope cannot log, then the auditor should check that a
Administrator and
8.5 4.16 Medium All. ISO27002 A.10.10.4 operator logs management process must be used instead or to supplement the change management process exists which records who logged on , when and for
required information (see above). what purpose and which retains the records for the appropriate period of time.
The auditor should review the CPs log of vulnerabilities or other appropriate
records ( e.g. suitably stored e-mails) showing information on vulnerabilities for
its Interconnect equipment. The auditor should check that a reasonable sample
of any vulnerabilities so far identified have either been patched, worked-around
The deployment of vulnerability solutions should follow change
management processes. Communications providers must have or assessed as unnecessary.
NGN, Control of technical Where this evidence leads the auditor believes that the CP may not be dealing
10.1 4.19 Medium ISO27002 A.12.6.1 policy and procedures for vulnerability management. Records
Internet vulnerabilities with vulnerabilities in a timely manner, the CP should be asked to demonstrate
should be kept of vulnerabilities identified and whether they were
its compliance to its change management procedures and processes for
patched, worked-around or dismissed as unnecessary to fix.
vulnerability management.
If no vulnerabilities have been discovered, the auditor should validate that the
relevant employees are aware of and understand the policy/procedure for
addressing the threats from vulnerabilities.
Information security events (which include loss of service,
equipment or facilities; system malfunctions or overloads; human
errors; non-compliances with policies or guidelines; breaches of 1. The auditor should validate that personnel within the scope of the Standard
physical security; uncontrolled system changes; malfunctions etc.) have been briefed on what constitutes a security event and on the reporting
should be reported through appropriate management channels as process. In a large company this might be formal training material, web based
Reporting information quickly as possible. information etc, whilst in a smaller CP it may be recorded as an agenda item
11.1 4.20 High. All ISO27002 A.13.1.1 security events Communications providers must have a process for reporting within team meetings. Where supporting evidence of a briefing is insubstantial ,
serious security events: the auditor should test the understanding of personnel in scope.
• through appropriate management channels; 2. The auditor should identify a recorded security event and validate this was
• externally where appropriate. reported effectively and appropriately
All personnel within scope should be fully briefed on how they
should report any security events.
1. The auditor should validate that the CP has a process for identifying serious
security incidents from events reported and notifying these:
• through appropriate management channels;
• externally where appropriate
Management responsibilities and procedures must be established
to ensure a quick, effective, and orderly response to information 2. The auditor should validate that personnel within scope are briefed on what
constitutes a security incident and on the reporting process.
security incidents.
Management of 3. The management involved should also be able to demonstrate an
11.2 4.21 High. All ISO27002 A.13.2.1 information security understanding of their responsibilities and use of procedure to provide a quick
incidents Communications providers must be able to describe the
and effective response. In larger organisations this may be more formalised with
management responsibilities and procedures for a quick, effective,
documented responsibilities ( i.e. within a job description) and processes. In
and orderly response to information security incidents affect assets
smaller organisation this might simply be key personnel describing how they
within scope. would deal with a security incident.
4. The auditor should identify a recorded security incident and validate this was
reported effectively and appropriately. The auditor should also validate that the
incident was dealt with in a timely and effective manner by management.
NOTES:
Internet peering is excluded
SS7 PSTN is excluded
Guidance ACTIONS
Where appropriate the CP may provide locations in generic form e.g. BT MUAs ,
where a common approach is adopted by the CP.
Any exceptions (see guidance notes) for which the CP is not seeking certification
must be clearly articulated in the scope with respect to the interconnect types , Generate example scope
services and locations they affect. This should also detail the controls which are
affected and the impact of the exception.
No specific template has to be used by a CP, as each approach may differ. The scope
may be defined in many ways: For example, to identify personnel CPs may just put a
category of staff, e.g. All Engineering Staff on the scope, or may choose to list
individual names, job roles or other categories as appropriate.
Exception information can be less detailed than that provided to the auditor but
must enable the 3rd party to understand which controls are affected , for which
interconnect types at which locations
The sample will be provided in the format most appropriate to the CP. No template is
mandated. Significant and material inaccuracies discovered during audit should be
considered a major non compliance
This ISP document could be the organisation’s overall information security policy,
standards and processes, and might comprise various sources and formats, such as
Word, HTML and PDF. However, CPs may choose to create a unique document (an
Interconnect Security Policy Document ) limited to those of its interconnects that fall
within the scope of the Standard.
The timeliness of management approval and communication will be a subjective
judgement of the Auditor based on the size and complexity of the CP, its processes
and supply chain.
The auditor is not expected to make a judgement on the quality of the ISP document
just that the controls within the Standard are covered and that measures are in place
to track these.
It is assumed that the quality of ISP document and the measures will ultimately be
reflected in whether audit is passed or not
The aim of the control is to demonstrate that management actively supports security
within the organization through clear direction, demonstrated commitment, explicit
assignment acknowledgment of information security responsibilities etc and actively
supports the implementation of and compliance with the minimum security
standard..
The acid-test on management commitment is ultimately whether or not the controls
are in place and functioning. A review should not be undertaken unless the auditor
has concern that such management commitment is lacking, based on evidence from
the audit.
The auditor should however be sensitive to the size of the organisation. Such
documentation described above may not be appropriate to a smaller businesses with
a more ‘informal’ approach. In such circumstances the auditor should ask individuals
identified as responsible to demonstrate their understanding of their responsibilities.
The auditor should be sensitive to the size of the organisation. Formal training and
communications approaches described above may not be appropriate to a smaller
businesses with a more ‘informal’ management style. In such circumstances the
auditor should ask for evidence of how responsibilities were briefed out e.g. emails, X
meeting notes etc but also by testing that individuals are aware of their
responsibilities.
CPs are not expected to seek to “force” suppliers to meet the Standard for existing
contracts unless this negotiated and agreed by both parties. The auditor should
review a sample of relevant contract documents, or other material, that supports the
obligations of the 3rd party to the CP to ensure these obligations have been
adequately cascaded. The auditor is not expected to audit the supply chain to
validate compliance. X
The auditor should consider for review any contract that is awarded from a date 3
months prior to the initial certification.
Note: The Standard states that a 3rd party may choose to obtain external
certification to demonstrate their compliance with the contracted controls, however,
at this time the scheme is not yet in place.
Where a 3rd party supplier is another CP certified to ND1643 and the services
provided are within the scope of its certification, then the CP being audited does not
have to provide further evidence of compliance but should demonstrate that its X
supplier CP has a valid certification
Where a 3rd party supplier is another CP certified to ND1643 and the services
provided are within the scope of its certification, then the CP being audited does not
have to provide further evidence of compliance but should demonstrate that its X
supplier CP has a valid certification.
These roles could be assigned in the policies, job descriptions or contracts. X
The 29th Feb 2008 date is from the start of additional requirements on employers
from the "Immigration, Asylum & Nationality Act 2006"
X
X
This unique identifier helps prevent accidental modification of the wrong equipment.
CPs may however decide to use an identifier other than their company name to help
reduce the risk of a targeted attacked
For smaller CPs it may be more appropriate for the CP to demonstrate the
effectiveness of the change process with the small number of individuals involved
which removes the need for more detailed procedures or documentation.
Audit logs are required to assist in future investigations and access control
monitoring. Review with NICC security group.
What exactly is required for best
If logs are not populated as a result of the youth of a system then the CP should security practice here?
demonstrate any recent log entry and the relevant settings for the storage period.
Administrator logs are required to assist in future investigations and access control
monitoring.
If logs are not populated as a result of the youth of a system then the CP should
demonstrate any recent log entry and the relevant settings for the storage period.
On some systems the audit logging controls and this, the administrator and operator
logs, may be identical.
Care should be taken to establish rules on the premise everything is generally Provide a simple example access
forbidden unless expressly permitted. control policy
Evidence of subscriptions to e-mails from vendors and other sources of security
information would be adequate in a smaller organisation, without the need for a
formal vulnerability management process.
A security incident is something that occurs (probably made of one or more events
reported from control 4.20) or is discovered which significantly affects the security of
the interconnect, your systems, or an interconnect partners.
Compliance reviews need not be a blanket approach. They may be various and
subject-matter specific, such as firewall rule-sets, administrator log history, on-site
checks that verify only authorised personnel are present, and so on. Compliance
checking provides the CP with a degree of assurance that risks are being mitigated,
and as such could be pragmatically programmed to cover areas of concern, or for
where no recent events or incidents have occurred. However, compliance with this
standard does need to be checked as a whole, albeit annually.
Change Log
1
2
3
4
5
6
7
8
Change Log
Should and may in control statements reviewed. Most should changed to must.
Date introduced for background checks. Review with CESG to confirm 224 compaibility.
Required logging information made more specific.
Format changed, guidance introduced.
Introduction of high / medium requirements. Guidance on how many mediums / highs can be failed
Slight change in wording to scope intiial control for clarity
Original wording from ISO removed.
Definition of security events and incidents refined. Additional guidance on what a security incident is.