CyberLifeCycleDiscuss your requirements
Menu
Discuss your requirements
Information

Service terms

From initial discussion to a proposal defining scope, roles and service conditions.

This page describes the commercial process. Commitments and terms arise from a proposal and contractual documents accepted before service starts. The website does not allow online ordering or payment.

Services offered

CyberLifeCycle offers professional clients a main managed vulnerability and software lifecycle service. It combines monitoring and assessment, context-based prioritisation, support tracking and documented remediation management within the agreed scope.

From requirements to proposal

A contact request prepares a scoping discussion. Scope, sources, authorised access, deliverables, schedule, frequency and financial terms must be specified in a separate commercial proposal before any service commitment. Pricing depends on scope, complexity and frequency.

The service is principally designed for ongoing annual management. Duration, renewal and termination, service hours and respective responsibilities are defined in contractual documents. Response times and service windows appear in the proposal.

Scope and responsibilities to agree

Tool exchanges depend on available formats, access and data. Authorised teams retain responsibility for technical implementation of fixes unless specifically contracted otherwise.

Traffic and data-protection analysis may form part of the service within the agreed scope. It covers analysis, recommendations and tracking. Intrusive testing, operation of information systems and network, architecture or configuration changes require a separate agreement.

Assessments, decisions and available evidence can support governance and audits. These deliverables document security management; they are neither certification nor a complete compliance assessment.

Matters to formalise

Final terms must specify provider identity, proposal acceptance, prices and taxes, invoicing, payment, scope changes, termination, confidentiality, ownership and use of deliverables, liability and dispute resolution.

Engagement documents must also define data minimisation, secure channels, access, personal-data roles where applicable, retention and return or deletion arrangements. These terms are adapted to the actual engagement.

Working with existing teams and providers

Collaboration with an IT service provider, current supplier or in-house team can be considered within the service. Roles, any subcontracting terms and commercial arrangements are defined in a separate written agreement.

Version dated 30 October 2026.