
Cyber insurance for SMEs: risks, preparation and policy questions
A small company can lose access to orders, invoices or correspondence even without an IT department. When considering cyber insurance for an SME in Moldova, begin with the work that would stop, not a package name. Record the systems used, who administers them and how work might continue without them.
This article is for managers of small or medium-sized shops, workshops, service firms and distributors. It is a practical preparation checklist, not confirmation that a suitable policy exists for every business. Cover, exclusions and acceptance must be checked in the specific proposal. Insurance does not replace security measures.
Map the path of a real order
Choose an ordinary order and follow it from the customer's message to payment. Where is information saved? Who issues the invoice? How does the warehouse know what to prepare? Record the applications and roles involved. Risk discussion then starts with actual operations rather than technical terms unrelated to daily work.
Identify what can temporarily be done manually and what depends on a single account. A manager's personal phone used for every confirmation can become a bottleneck. Do not publish detailed network diagrams or login details. An initial discussion needs a functional description, not information that could facilitate an attack.
Separate company accounts from personal accounts
List important email, accounting, stock, domain and payment-service accounts. Record the account holder and responsible role. If a former employee created an account with a personal address, clarify recovery and administration before a problem arises. Do not send passwords to a broker as evidence that an inventory has been completed.
STISC recommends access protection and multifactor authentication where available. Put simply, login then depends on more than a password. The company must also know who can recover an account when the main person is absent. Ask the IT specialist for a secure, documented procedure suited to the services used.
Check a backup, not only its existence
A backup is useful if required data can be restored in an appropriate environment. Ask what is actually copied: documents, order databases, settings or only selected folders. An automated completion message alone does not explain whether the company can resume work using those files.
Arrange a limited restoration test with IT staff without deleting or interrupting the production system. Record the date, data checked and remaining uncertainties. Do not present the test as security certification. It is concrete evidence of a restoration operation under the conditions in which it was performed.
Establish the IT provider's responsibilities
A maintenance contract may cover only part of the infrastructure. Compare the application list with the services undertaken. Who updates systems, manages access and responds outside office hours? Request roles and contact channels rather than a general promise that someone handles everything.
Keep prevention, technical response and any insurance separate. A monthly support invoice does not establish that the provider bears every commercial loss. Its own policy does not confirm that your business is insured either. Read each relationship's contract, beneficiary provisions and applicable limits.
Describe interrupted work through activities and records
Instead of unsupported loss estimates, describe what cannot be done: issuing invoices, preparing orders, taking payments or accessing work records. Distinguish delayed orders from cancellations. Gather documents that could explain the difference rather than inventing a percentage of lost revenue.
Record ordinary expenses and potential additional costs of alternative working arrangements. This supports planning and insurance discussion but does not mean every cost will be accepted. A business-interruption provision must be examined for its triggering cause, period and documents, not only its name.
Not every fraud is the same as a cyber incident
A compromised account, altered invoice and mistakenly authorised payment can involve different mechanisms. Explain separately how the transaction began and who approved it. Do not assume a product called cyber automatically includes transfer fraud or a payment error. Request an explanation for the particular scenario.
A business may introduce an additional check of changed bank details through a known channel. This is an organisational recommendation, not a universal insurance condition. If fraud is suspected, involve the bank and appropriate specialist promptly without publicly sharing payment documents or personal details.
Prepare a short assessment summary
Include the activity, approximate number of system users, essential applications, administrators and existing backup arrangements. Answer the insurer's questions accurately. A business without documented procedures must not be described as having tested controls merely to obtain a proposal faster.
Discuss incident history and known circumstances confidentially. Start with a description without personal data, then agree which documents are needed and how to send them. Do not attach customer databases, passwords, API keys or complete message histories to a public quotation form.
Read limits before comparing the premium
The insurance premium is the amount paid for insurance. Compare the same activity and scenarios. Ask about limits for each cost category, deductibles and exclusions. The deductible is the insured's own share under the contract; do not infer it from a marketing example.
Ask who authorises an expert's intervention and what happens if the usual supplier begins work before approval. Do not delay urgent personal-safety measures or authorities' instructions. For claims procedures, follow the applicable documents and instructions rather than assuming a universal deadline found in an article.
A tabletop exercise for the manager and accountant
Choose a simple scenario: one morning the email account used for orders is inaccessible. Without blocking the real account, discuss who notices, who informs the provider and how existing orders are checked. Use fictitious information and do not interrupt operations or send misleading messages to customers.
Record the outcome in four columns: observation, responsible role, action and confirmation. If nobody knows how to contact the provider without the main email account, that is a concrete organisational problem. Do not hide it in the insurance description. Establish and test a secure alternative without publishing personal numbers or recovery information.
Separate emergency contacts from system access
A contact list should be kept in an agreed place accessible to authorised staff without depending on the same account that might fail. It must not contain passwords. Ask a technical specialist to provide secure backup access. Do not improvise a shared file containing every company secret merely because it is easy to find.
Establish who can approve urgent expenditure and who retains supporting records. Internal authorisation and approvals required by a policy are different. A technical-support invoice is not automatically an accepted claim expense. Before buying insurance, ask how external providers are engaged and what incident-notification information is required.
Review access for people who no longer work at the company
Arrange periodic checks of access belonging to employees and contractors who have left or changed roles. Do not hastily delete accounts and files without understanding business needs and retention obligations. Coordinate the review with competent staff. The aim is to reduce unnecessary access without losing documents or blocking services.
Describe management and loss-reporting arrangements for devices used outside the office. A personal phone or laptop used for work may differ from a company-managed device. Do not claim every device has the same controls without checking. State clearly what is known and what still needs an inventory.
A minimum assessment file is not a public database
Prepare a one-page overview and unanswered questions for the initial discussion. Detailed documents can be selected later following a justified request. A full customer database is not a substitute for describing data categories. Keep sensitive business information separate and use anonymous examples when explaining an order or invoice process.
- Essential activities and supporting applications.
- Internal responsibility and the IT provider's services.
- Existing controls, without claiming planned functions already operate.
- Restoration tests and their documented limitations.
- Fraud scenarios requiring separate assessment.
- Questions about costs, limits and incident notification.
After clarification, request a written proposal summary and retain the documents reviewed. If the business profile changes, such as adding an online shop, review the information before assuming identical protection. An updated file supports discussion; acceptance and conditions are the insurer's decision, not the checklist author's.
Frequently asked questions from small businesses
We only use email and accounting. Is there still a risk?
Consider dependence on those services and what can continue without them. A small application count alone does not show the impact of an interruption. Assessing risk does not automatically establish product eligibility.
Does insurance replace antivirus software or backups?
No. They serve different functions. Technical and organisational measures reduce exposure; an insurance contract is checked separately for accepted events and costs.
Can we obtain a price without system information?
A useful price requires the information needed to assess the company. This article gives no guaranteed rates or discounts. Clarify activities, existing measures and uncertainties before comparing a specific proposal.
Next step
Request a discussion with ING Broker to check assessment and intermediation possibilities. The broker explains options and intermediates; acceptance, conditions and claims decisions belong to the insurer under the contract. This article does not confirm product availability or cover for an individual event.
Read also: Cyber insurance for companies: general checks.
Sources and limits of this information
The Romanian source consulted these sources on 9 November 2026. Preparation lists are editorial recommendations, not policy conditions. Examples belong to the cited providers and are not an ING Broker offer. Legal obligations and individual situations require specialist verification.
