CGI - Event Archive

Our Event Archive service enables users to retain and retrieve audit, security, server, firewall and similar records in a cost effective, secure, efficient and timely manner. Typical client applications resulting in increased productivity include operational data stores and traditional log file archives.


  • Flexible Data Ingest includes CSV, XML and JSON formats
  • Data Retrieval via ODBC, JDBC, RDHI or REST interfaces
  • Automated Purging of data on expiry of commitment
  • Standard PKI for authentication, encrypted storage and data transfers
  • Application level replication provides for Business Continuity and Disaster Recovery
  • Ingest 14,000 records per second on a single CPU core
  • Retain 10TB raw input data using only 16TB RAID5 storage
  • Purge 14,000 records per second on a single CPU core
  • Sectors: Justice, Policing, Prosecution, Courts, Prisons, Probation, Central Government, Education


  • Load more than five billion records a day.
  • Records ready to be queried under ten minutes after loading.
  • Search results returned in seconds.
  • Handles multiple data formats which can change over time
  • No need for expensive specialist hardware
  • Original data always retained to provide evidential integrity.
  • Simple management and operation
  • Store 10TB of raw data in a 16TB repository.
  • No third-party product licences


£7000 per licence per month

Service documents


G-Cloud 11

Service ID

4 5 6 0 1 5 2 3 7 6 1 4 1 7 8



Roger Baileff

07841 602596

Service scope

Software add-on or extension
Cloud deployment model
Hybrid cloud
Service constraints
The service is designed to be available 99.7% of the time .
Notification of planned maintenance will be provided at least 24 hours in advance and six hours notice of emergency maintenance will be provided where possible. Maintenance windows are between the hours of 17:30 and 09:00 (UK local time) on a normal business day and/or between the hours of 08:00 and 12:00 (UK local time) on a non-business day.
System requirements
  • One CPU core for every 14,000 events per second ingested
  • 16TB storage for every 10TB raw data to be retained

User support

Email or online ticketing support
Email or online ticketing
Support response times
Priority 1: within 30 minutes.
Priority 2 : within 1 hour
Priority 3: within 4 hours
Priority 4: within 8 hours from receipt of call
User can manage status and priority of support tickets
Phone support
Phone support availability
9 to 5 (UK time), Monday to Friday
Web chat support
Yes, at an extra cost
Web chat support availability
9 to 5 (UK time), Monday to Friday
Web chat support accessibility standard
None or don’t know
How the web chat support is accessible
The system is based on Avaya Automated Chat 2.0 (formerly Conversive). Details on accessibility can be found at:
Web chat accessibility testing
Testing would have been performed by Avaya the product vendor
Onsite support
Yes, at extra cost
Support levels
"Priority 1 Respond within 30 minutes, resolution or work-around within 24 hours
Priority 2 Respond within 1 hour. resolution or work around within 3 Working Days
Priority 3 Respond within 4 hours, resolution or work around within 10 Working Days & Permanent Solution in next release
Priority 4 Respond within 8 hours, resolution or work around within 30 Working Days & Permanent Solution in next major release"
Support available to third parties

Onboarding and offboarding

Getting started
A typical on-boarding project takes about 4 or 5 months and consists of:
A Discovery phase which documents and prioritises the data feeds which will be ingested by the Event Archive and how the data will be retrieved. Hosting and security aspects are also discussed and agreed. This can be expected to take 4 to 6 weeks to complete, using two to three sprints. It defines an agreed, prioritised scope for the remainder of on-boarding project.
An Alpha phase delivers an Interim Operational Capability whose scope is limited to a small proportion of the data feeds and query mechanisms. This is not just a prototype – the parts that are included are fully functional. It is normally followed by a review at which the scope and priorities for the remainder of the on-boarding are agreed.
A Beta phase delivers the Final Operational Capability with the full agreed scope. This may include some re-work of the Alpha delivery as agreed at the review. The duration of the Beta phase depends on the complexity and numbers of ingest data feeds and query mechanisms, as well as the security architecture and any penetration testing required.
Service documentation
Documentation formats
End-of-contract data extraction
A request can be made for the data held in the archive to be extracted at additional cost.
Data is exported in CSV format
End-of-contract process
All input data feeds will be stopped so that no more data is ingested or retained.
Retrieval and Admin (if applicable) access will be revoked. Data will be purged from the system using standard functionality.

Using the service

Web browser interface
Application to install
Designed for use on mobile devices
Service interface
What users can and can't do using the API
Upload data to be retained using Secure FTP.
Query the data in a generic manner, including from tools that support ODBC or JDBC using SQL interface.
Submit internationally standardised queries, check on their progress and retrieve the results using RDHI, XML and REST interfaces.
Monitor the state of the system using SNMP.
Start, stop, reconfigure and administer the system using the management API
API documentation
API documentation formats
API sandbox or test environment
Customisation available
Description of customisation
CGI does not recommend that first time users try to configure the DRD service themselves.
The Discovery phase of the on-boarding project determines and prioritiese which data feeds need to be provided and the data retrieval mechanisms required.
CGI will provide interim operating capability (IoC) in the Alpha phase and is happy to work with users in the Beta phase to further configure the service with a view to users being able to do this for themselves in the future.
System Administration and User Training is available at additional cost


Independence of resources
CGI has a sizing model for its Event Archive which is used to calculate the compute and storage resource requirements for each installation. This is shared and agreed with each customer in the Discovery phase of every on-boarding project and reviewed again after the Alpha phase.
Similarly, there is a sizing model for support resources which is used internally to ensure there are enough support resources to service all installations.


Service usage metrics
Metrics types
The Administration system produces real time statistics on the Procecsses currently running, storage used and parameters configured. The GUI interface also provides access to error and audit logs, Users and Groups.
Usage can also be monitored in real time. This includes CPU, disk I/O nad disk space but also:
* Batch and record load rates
* Load latency (freshness of data)
* Query (and slow query) rates
* Total batches, cases, alerts and records
* Uptime
* Database interface stats (total and current connections, bytes sent and received, failed connections)
* Bad, empty and duplicate batches and records
Reporting types
  • Real-time dashboards
  • Regular reports


Supplier type
Not a reseller

Staff security

Staff security clearance
Other security clearance
Government security clearance
Up to Developed Vetting (DV)

Asset protection

Knowledge of data storage and processing locations
Data storage and processing locations
United Kingdom
User control over data storage and processing locations
Datacentre security standards
Managed by a third party
Penetration testing frequency
Less than once a year
Penetration testing approach
‘IT Health Check’ performed by a CHECK service provider
Protecting data at rest
  • Encryption of all physical media
  • Scale, obfuscating techniques, or data storage sharding
  • Other
Other data at rest protection approach
Other methods of protecting data at rest will be discussed with the hosting provider and agreed during the Discovery phase of the onboarding project.
Data sanitisation process
Data sanitisation type
Explicit overwriting of storage before reallocation
Equipment disposal approach
A third-party destruction service

Data importing and exporting

Data export approach
Data export is an integral part of the service. Data returned by User queries run in the GUI can be exported in CSV or pdf format.
Data export formats
  • CSV
  • Other
Other data export formats
Data import formats
  • CSV
  • Other
Other data import formats
  • JSON (at additional costs)
  • XML (at additional costs)

Data-in-transit protection

Data protection between buyer and supplier networks
  • Private network or public sector network
  • TLS (version 1.2 or above)
Data protection within supplier network
TLS (version 1.2 or above)

Availability and resilience

Guaranteed availability
The service is designed to provide 99.7% availablity and to ensure zero data loss
Approach to resilience
CGI recommends that two copies of each processor and each data store be located at geographically separate sites. Application level replication between the Primary and Secondary instances ensures that these installations are synchronised effectively providing two production copies of the live service.
This architecture also provides for Disaster Recovery and Business Continuty.
Outage reporting
Alerts are generated at application level and notified to the Support Centre
The system is also monitored using SNMP and alerts raised at the datacentre. Incidents and Problems are managed by the service desk within the Support Centre.

Identity and authentication

User authentication needed
User authentication
  • Public key authentication (including by TLS client certificate)
  • Limited access network (for example PSN)
  • Username or password
Access restrictions in management interfaces and support channels
Access to the application through the GUI is controlled using role based access control. A user must provide an Id and a (strong) Password or certificate. Passwords expire after a configurable time.
Within the system users are allocated to Groups which have permissions to execute certain functionality. Groups and their capabilities are defined by the System Administrator.
Users, Groups and roles will be described and agreed in the Discovery phase of the on-boarding project.
Access restriction testing frequency
At least every 6 months
Management access authentication
  • Public key authentication (including by TLS client certificate)
  • Limited access network (for example PSN)
  • Username or password

Audit information for users

Access to user activity audit information
Users have access to real-time audit information
How long user audit data is stored for
At least 12 months
Access to supplier activity audit information
Users contact the support team to get audit information
How long supplier audit data is stored for
At least 12 months
How long system logs are stored for
At least 12 months

Standards and certifications

ISO/IEC 27001 certification
Who accredited the ISO/IEC 27001
AFNOR UK Ltd (UKAS Registration No.022)
ISO/IEC 27001 accreditation date
What the ISO/IEC 27001 doesn’t cover
Nothing is NOT covered.
The following IS covered from a Technical perspective: Provision of outsourcing sevices including managed infrastructure services, contact centre services, service desk services, management of print and email, application development, maintenance and support services.
The following IS covered from a Business perspective: The provision of outsourcing, project and consultancy services, including development and delivery activities, plus the management of people, technologies and physical security.
ISO 28000:2007 certification
CSA STAR certification
PCI certification
Other security certifications

Security governance

Named board-level person responsible for service security
Security governance certified
Security governance standards
ISO/IEC 27001
Information security policies and processes
Our security, information security and data protection management system for CGI is established through the Enterprise Security Management Framework (ESMF). The framework applies to the work we conduct for ourselves and for clients under UK contracts. All CGI UK members and contractors are expected to comply with its principles and processes.

The ESMF is comprised of:
A first level suite of security policies and security requirements that apply across the CGI enterprise.

A second level set of standards set out how these policies and requirements are met, these being detailed within the following operational categories:- Access Control- Operations- Technology- Applications- Data management- HR and Organisation- Physical"

Operational security

Configuration and change management standard
Supplier-defined controls
Configuration and change management approach
The Support Centre uses Subversion for Version Control and Trac for issue tracking. Change Requests are managed as tickets in Trac.
Change Management process is summarised below:
The client makes the request to the service desk (including when it is required by)
Service Support provides an Impact Assessment and a man-day estimate and timeline
On confirmation of acceptance, the change is planned and the release and/or patch date confirmed
Vulnerability management type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Vulnerability management approach
All CGI and customer managed systems are kept current with vendor patches (both operational and security) with vulnerability tests performed regularly. Systems are prioritized based on criticality of known vulnerabilities. All changes are strictly controlled through CGI’s change management process.
Protective monitoring type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Protective monitoring approach
Please see the CGI - Security Operations Centre (SOC) - Protective Monitoring Service for full details of these processes
Incident management type
Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402
Incident management approach
CGI has a very well-defined security incident management standard and supporting process to handle all phases of a security incident. Responsibilities are clearly defined at all levels. Priorities are established to ensure the timely resolution of incidents. Records of incidents are maintained and reported to senior management. Incidents considered to be severe (high priority) are managed through CGI’s Incident Management Centre (IMC), who coordinate/escalate all required parties based on priority. Collection/preservation of evidence is carefully observed throughout the process.

Incident exercises are performed regularly to ensure the process works as expected when needed.

Secure development

Approach to secure software development best practice
Supplier-defined process

Public sector networks

Connection to public sector networks


£7000 per licence per month
Discount for educational organisations
Free trial available

Service documents

Return to top ↑