Technician checking data-centre equipment with a tablet
Updated: 16/11/2026
ING Broker editorial team

Data centre insurance: equipment and continuity

A data centre should be assessed as a system of interdependent equipment and services. Servers, electrical supply, cooling, the building and obligations towards customers are different insurance subjects. For a Moldovan company, preparation begins with the inventory and a technical interruption scenario. A combined value alone does not explain how those assets and services depend on each other.

This article helps data-centre operators, server-room owners and companies buying colocation services. Colocation means hosting equipment in premises managed by another operator. It does not confirm availability of a product for every infrastructure. Conditions require verification for the actual site, devices and services, rather than acceptance inferred from the data-centre name.

Define space and activity

Describe whether the assessment concerns an internal company room, a commercial hosting centre or a network of sites. Record who owns the building and operates installations. Include relevant auxiliary areas, not only server rows visible in a promotional photograph. The file should show the actual boundaries of the location under consideration.

Separate physical hosting, administration, storage and support services. If only space and power are provided, do not describe operations as though the company controls customer applications. Conversely, disclose system administration where it exists. Risk assessment starts with what the company actually does, not just the centre's name or an assumed industry profile.

Separate inventory by ownership

Prepare distinct lists for owned, leased and customer equipment. Confidential records should include serial numbers or other internal identifiers, locations and value documents. An initial discussion can use a category summary. Do not publish detailed infrastructure or customer inventories in an open form merely to demonstrate completeness of the assessment file.

Ask for clarification of the insured interest for each category. A server being inside the building does not confirm inclusion under the operator's policy. A customer agreement may set responsibilities but needs review separately from insurance. Do not duplicate or remove values without explaining the inventory basis and the relevant ownership arrangements.

Equipment value differs from data value

A server, software licence and stored information are different elements. In the property inventory, identify physical components and records supporting their values. For data, describe recovery processes and technical dependencies. Do not assign an arbitrary amount to a database merely to complete an insurance field. The value basis should be clarified, not invented.

Separate replacement of a component from reconfiguration, migration and service checks afterwards. Procurement time may differ from the time needed to restore working service. This information supports internal planning. It does not by itself confirm that all expenses or affected revenue are insurable or accepted in an offer.

Follow the electrical supply path

Describe the main source, internal distribution and backup equipment actually present. A UPS is an uninterruptible power-supply device; its duration and function need technical verification against the real load. Do not declare autonomy using only a manufacturer label or the configuration at installation. Request relevant records and tests from the technical specialist.

Record maintenance, responsibility and common components in paths described as independent. Two inputs must not be presented as guaranteed continuity without checking the configuration. For insurance, distinguish damage to owned equipment from external-service interruption. A cause and its consequences are assessed under actual product conditions, not an assumption based on the number of feeds.

Cooling must match actual load

Identify cooling installations, monitoring and response to an alert. Mention changed loads and recent expansions. Do not use an old centre presentation if infrastructure has changed. Work with the designer or a competent specialist on technical values and tolerances, not with a generic article example. The insurance description should reflect today's configuration.

Retain work records and relevant incidents, including unresolved findings. A recorded alarm does not automatically prove an intervention occurred. Internally track who receives the alert and who confirms closure. A clear history is more useful than an unsupported statement that installations are monitored continuously. Keep the observation distinct from the action taken.

Physical security differs from data security

Building access, rack access and system access can be managed differently. Describe arrangements for employees, customers and subcontractors. A rack is the technical cabinet containing equipment. Do not publish access plans, codes or the precise location of sensitive elements to prove controls exist. Use a general description initially and agree justified detail separately.

For fire, water and other physical risks, provide the configuration and requested records without inventing legal requirements. Specialist technical review and policy conditions are distinct checks. Do not present an existing installation as compliant with a standard nobody has verified. Its existence also does not confirm payment of every resulting claim.

Recovery needs a sequence

Identify priority services and dependencies that must be restored first. Separate infrastructure restart from confirmation that a customer's application works correctly. For colocation, show where the operator's role ends and the customer's begins. A telephone list without a cooperation procedure is not the complete recovery plan, even where every contact is up to date.

If an alternative site exists, explain what it can actually take over and what must be transported or reconfigured. Do not claim complete continuity where a plan covers selected services only. Arrange controlled exercises without endangering production or data. Record results together with the limits and conditions under which the test was performed.

Customer contracts need separate review

Prepare model customer agreements and service-level annexes. Identify downtime calculation, incident communication and any contractual compensation. Do not assume property insurance automatically pays penalties or customer claims. These sums require separate discussion against the documents and availability of an appropriate solution. A service promise and an insurance condition are not the same document.

Also provide essential-supplier contracts to understand risk remaining with the operator. A subcontractor having a policy does not prove protection for your company. Before comparing price, request boundaries between property, restoration costs, interruption and liability. Mark what is unconfirmed explicitly rather than treating one supplier's insurance as a response to all residual obligations.

Plan component replacement without time promises

Choose critical equipment and map complete replacement: identification, procurement, transport, installation, configuration and verification. Do not stop a production system for an editorial exercise. Discussion with technical staff can reveal missing parts and records. A supplier's period must not be presented as guaranteed service recovery or settlement time for an insurance claim.

For equipment no longer sold, retain explanations of compatible alternatives and the valuation basis. Do not automatically assign the same price to a replacement with another function. Before establishing a sum insured, clarify the accepted method and necessary evidence. An internal technical estimate is assessment information, not a value contractually confirmed by the insurer.

Maintenance and configuration changes

Work on power or cooling may temporarily change operating conditions for several devices. Internally record the work window, approval, provider and subsequent checks. Scheduled maintenance is not free of consequences merely because it appears in a calendar. The record should show what was done and who confirmed its result, not just that an intervention was planned.

After significant component replacements, update documents and check what must be communicated for insurance. Do not mix retired property with equipment installed later. Clear inventory versions help identify circumstances on an event date. They do not replace approval of a contractual amendment where the actual proposal requires one. Internal records and insurer confirmation serve different purposes.

Respect continuity-demonstration limits

An exercise may confirm that a specific backup path worked under a precise configuration and load. Do not extend that conclusion to every service or incident. Retain the objective, conditions, participants by role and untested elements. A publicly distributed report should exclude unnecessary personal information and sensitive site details. The limits are part of the evidence.

For commercial assessment, distinguish the operator's work from customer activities after infrastructure recovery. The customer may need its own checks and configuration. Do not describe the whole process as one person's task where responsibilities are shared. Clear boundaries support questions about costs and liability without confirming cover for an actual loss.

Prepare assessment and renewal summaries

At renewal, compare current inventory with the version used previously. Record expansion, retired equipment, customer or service changes and relevant incidents. Do not automatically reuse an old form after infrastructure changes. Review documents with competent technical and financial staff, and mark information not confirmed before presenting it as fact.

  • Sites and ownership boundaries.
  • Value evidence and proposed valuation.
  • Actual power, cooling and maintenance.
  • Critical services and continuity-test limits.
  • Customer and essential-supplier contracts.
  • Separate property, interruption and liability questions.

The initial file need not expose the entire architecture. Agree what level of detail is justified and how it will be transmitted confidentially. On receiving a proposal, check whether it describes the actual system and whether uncertainties were resolved in writing. A good technical presentation supports assessment without promising issue or compensation.

Frequently asked questions about data centres

Does building insurance include all servers?

Location alone does not establish it. Check subject, owner, inventory and values, especially customer equipment.

Does backup power eliminate interruption risk?

No. Configuration, maintenance and failures require technical review. Reserves are not a guarantee of operation or cover.

What should we prepare?

Ownership inventory, sites, dependencies, maintenance and contracts. Never send passwords, detailed security diagrams or customer data through public channels.

Next step

Request a discussion with ING Broker to check assessment and intermediation possibilities. The broker explains options; acceptance, conditions and claims decisions belong to the insurer under the contract. This article does not confirm availability or individual cover.

Read also: IT equipment inventory before insurance.

Sources and limits of this information

The Romanian source consulted these sources on 9 November 2026. Lists are editorial recommendations, not policy conditions. Examples are not an ING Broker offer. Legal obligations and individual situations require specialist verification.

Data centresMoldova