## Validation (Imcv) Component Statement Of Applicability Validated Component Summary

Name: 
Ionics Isapi Rewrite Filter (IIRF) 
 
 
Version: 
Version v1.2.15 
 
 
Validation Completed: 
29th March 2009 
 
 
Validation 
Facility: 
Enex Testlab 
 

## Information Management Component Validation

The National Archives is a government department and an executive agency under the Secretary of State for Justice, which has statutory and policy responsibility for Knowledge and Information Management (IM) for public sector information.   It therefore sets standards and supports innovation on information management across the UK, in order to ensure the survival of records in whichever form they are created, be it paper or digital, and provides practical frameworks of best practice for use of public sector information. In recognition that almost all the information created in government is now electronic, but that there is a risk that information risks becoming inaccessible as technologies and organisations change, the National Archives has been leading work on digital preservation as acknowledged in the Transformational Government Implementation Plan. The National Archives has therefore generated a technical framework for Information Persistence for government departments and the public sector, to ensure the long term survivability of records from any systems, and guard against compromises of Integrity and Availability. As part of this framework, a formalised system of validation of technical components has been established, to provide Stakeholders with confidence that such technologies have been independently reviewed for fitness for purpose. 

 

## Component Overview

IIRF (Ionics Isapi Rewrite Filter) is a free software tool available from Codeplex 
(http://www.codeplex.com/IIRF). The tool has been sourced by the Stationery Office (TSO) 
in order to provide software that can help government departments manage URL persistence. IIRF is installed on Microsoft web server platforms to add URL rewriting and redirection functionality to IIS, which does not provide this functionality natively. 

 

## Component Statement Of Applicability Validation Deployment Scenario

 
The component is expected to be deployed on Microsoft web servers across central government departments.  This may include servers owned and managed directly by the departments, servers managed by IT suppliers, or servers set up under arrangements such as co-location and virtual hosting. 

There are expected to be one or more competent individuals in each implementing department (or their suppliers) assigned to manage the implementation of the product, and the initial and ongoing configuration of the implementation rules. Those personnel are not careless, willfully negligent, nor hostile. The environment is expected to include a set of  Pragmatic, Appropriate and Cost Effective (PACE) controls, in terms of a balanced set of Personnel, Physical, Procedural and Technical (P3T) measures, to mitigate the Risks arising from the various Vectors (e.g. 

unauthorised access, physical damage, information release and malicious software) from various types of Adversity (e.g. directed Threats, such as Attacks, and collateral Hazards, such as extreme climatological events).

 

## Validation Environment

The Component has been tested Windows Server 2003 (including R2) with IIS6 and Windows Vista SP1 with IIS7. 

## Component Statement Of Applicability Controls Provided

The component provides support for the technical controls listed below, provided the deployment is commensurate with the assumptions, and that the overall organisational policies are supportive.  Use of the product alone should not be taken to infer in any way compliance with the listed standard. 

| Control Title                                                        | Control Details                               |
|----------------------------------------------------------------------|-----------------------------------------------|
| Standards                                                            |                                               |
| Cross                                                                |                                               |
| Reference                                                            |                                               |
| ISO/IEC 27001                                                        |                                               |
| A7.1.1                                                               |                                               |
| Inventory of Assets                                                  | All assets shall be clearly identified and an |
| inventory of all important assets drawn up and                       |                                               |
| maintained.                                                          |                                               |
| ISO/IEC 27001                                                        |                                               |
| A.10.5.1                                                             |                                               |
| Information back-up Back-up copies of information and software shall |                                               |
| be taken and tested regularly in accordance with                     |                                               |
| the agreed backup policy.                                            |                                               |
| ISO/IEC 27001                                                        |                                               |
| A.10.8                                                               |                                               |
| Information                                                          |                                               |
| Exchange                                                             |                                               |
| System shall only release information (eye                           |                                               |
| readable or non eye readable) to authorised                          |                                               |
| person(s)                                                            |                                               |
| ISO/IEC 27001                                                        |                                               |
| A.15.1.3                                                             |                                               |
| Protection of                                                        |                                               |
| organizational                                                       |                                               |
| records                                                              |                                               |
| Important records shall be protected from loss,                      |                                               |
| destruction and falsification, in accordance with                    |                                               |
| statutory, regulatory, contractual, and business                     |                                               |
| requirements.                                                        |                                               |
|                                                                      |                                               |

## Validated Claims

The following specific functionality has been successfully tested in the environment and usage scenario as described above: 

| Ref                                                                              | Claims Statements                                                                    |
|----------------------------------------------------------------------------------|--------------------------------------------------------------------------------------|
| IIRF01                                                                           | The component uses an ini file in which URL rewriting and redirection rules can      |
| be programmed by users.                                                          |                                                                                      |
| IIRF 02                                                                          | The component can be programmed to rewrite or redirect one or more individual        |
| URLs, and/or all URLs matching one or more specified patterns, using the         |                                                                                      |
| PCRE syntax.  Different rewrite/redirection behaviours can be specified for each |                                                                                      |
| URL or group of URLs affected. Redirection rules can both include and exclude    |                                                                                      |
| URLs from rewriting or redirection.                                              |                                                                                      |
| IIRF 03                                                                          | Redirection configuration INI files cannot be modified or adversely affected         |
| through use of malicious URL injection methods.                                  |                                                                                      |
| IIRF 04                                                                          | When using "RedirectRule" OR "RewriteRule" entries to specify URL patterns           |
| for redirection, the component functions with URL and query string lengths       |                                                                                      |
| within the limits supported by the server software.                              |                                                                                      |
| IIRF 05                                                                          | On multi-site IIS installations, the component can be installed either for all sites |

 

## Validation (Imcv) Component Statement Of Applicability


collectively, or for one or more sites individually. 
IIRF 06 
The redirection component makes no modification to the content of the page, 
only to the URL 
IIRF 07 
Rewrite activity can be logged to files on a directory specified by the user if 
desired. This does not affect the main IIS logging. 
IIRF 08 
The component has support for Unicode, URL characters, and UK and foreign 
language content in use on central government websites, based on redirection 
rules written in the English language. 
IIRF 09 
Installation of product introduces no known malicious software into the system 
IIRF 10 
The component makes no alteration to the original case of the URL unless 
specifically programmed to do so in the ini file. 
IIRF 11 
The tool communicates directly only with the web server(s) on which it is 
installed and attempts no direct communication with external systems. 

  

## Publicly Known Vulnerabilities

No publicly listed vulnerabilities from either the Common Vulnerabilities and Exposures 
(CVE) database or the (US) National Vulnerability Database (NVD) were found to apply to this component at the time of testing. 

 

## Operational And Risk Management Considerations

Although the component will run on various other Windows and IIS platforms, the Claims validated here relate only to the versions specified. In deploying and operating the Component, it is assumed that Information Assurance (IA) risk assessment to either system and/or the data it is envisaged to handle attracts no higher baseline requirement than that derived from the UK National Annual Threat Assessment (ATA) and the UK National Strategic Risk Assessment (NSRA) / National Risk Planning Assumptions (NRPA). It is furthermore assumed that the risk management measures already put in place for corporate infrastructure(s) on which the Component is deployed have mitigated any increased differential risk factors to a level commensurate with the application of baseline measures. 

 


## Information Management Component Validation (Imcv) Component Statement Of Applicability

 

## Component Statement Of Applicability

The Component described in this document has been independently assessed by 
the listed Validation Facility, which is a Test Laboratory approved by the UK 
Accreditation Scheme (UKAS) under ISO/IEC 17025:2005 "General requirements for 
the competence of testing and calibration laboratories". 
 
This Claims made for the Component, and the Testing, have been subjected to 
scrutiny by a Technical Authority within the National Archives, in their capacity as 
the government department having statutory and policy responsibility for 
Knowledge and Information Management (IM) of public sector information.   
  
It has been concluded that, when installed, configured and operated correctly, as 
described in associated documentation and herein, this Component is suitable for 
performing the Claimed functionality in support of public sector IM activities, 
subject to the operational and risk management considerations noted herein. 
 
The information has been provided in good faith, and is based on the component 
version and usage scenario(s) as detailed in this document. This information is not 
therefore designed for any particular implementation, and we therefore cannot 
guarantee accuracy or relevance for any specific purpose.  The Validation Testing 
is not a guarantee of freedom from security vulnerabilities. There remains a 
probability that exploitable security vulnerabilities may exist in any Product or IA 
Service, or the IS environment supporting such a Product or Service. 
 
We do not accept responsibility for any information omitted, or errors in this 
information.    We do not have any responsibility for the accuracy, availability, 
completeness or usefulness of any of the information provided. 
 
No other terms, conditions, representations or warranties will apply. 
 
References we make to any specific product, process or service by trade name, 
trademark manufacturer, or otherwise, or linking to other websites or material are 
not endorsements or recommendations. 
 
The views and opinions of the National Archives shall not be used for advertising or 
product endorsement purposes.   This information is for official purposes, and the 
contents may not be used for commercial purposes. 

## Approved By

Ian Bryant 

IMCV Technical Authority 
27th April 2009