A plain-language guide to the cloud, data centre, cybersecurity, backup, network and infrastructure terms we use at Seintec.
Technology explained so you can decide with confidence
At Seintec we work with cloud, infrastructure, networks, cybersecurity and business continuity every day. We know many of these concepts can feel opaque if systems are not your field.
That is why we built this IT glossary: to explain, clearly and accurately, the terms we use across our website and in our projects.
The goal is not to turn you into an IT specialist. It is to help you understand what you are buying, why it may matter to your business and which questions are worth asking before a technology decision.
73 terms
Backup & continuity
3-2-1 rule
A backup best practice: keep three copies of your data, on two different media, with one of them off-site. It is the minimum benchmark so a local incident cannot hit every copy at once.
A filter that inspects inbound and outbound email to block unwanted messages, impersonation attempts and dangerous attachments before they reach the mailbox. It cuts phishing risk and daily noise alike.
Software that detects and blocks malicious programs on devices and servers. In a business environment it must be centrally managed: deployment, updates, exclusions and alerts someone actually reviews.
A separate copy of data and systems kept so they can be recovered after deletion, a technical failure or an attack. A backup is only valid if restores are tested regularly.
In practice
Run at least one real restore test a year and record how long it took.
How much data a connection can carry per unit of time. For a business, upload capacity and stability usually matter more than the headline download figure.
A company's ability to keep operating during an incident, not just to recover systems afterwards. It covers processes, people and fallback ways of working as well as technology.
In practice
If the warehouse cannot invoice, it may need a temporary manual procedure while the system is restored.
A model where a company consumes servers, storage or applications from a data centre instead of running them on its own premises. You pay for the capacity you use and hardware upkeep is no longer your responsibility.
In practice
A mid-sized company can move its file server and ERP to a data centre and reach them from any site.
The process of moving servers, applications and data from an existing environment to a cloud platform. A sound project starts with an inventory, defines downtime windows and plans a rollback.
In practice
Before migrating an ERP it is worth testing start-up in the new environment with a real copy of the data.
Hosting a company's own servers in a provider's data centre, which supplies space, power, cooling, connectivity and physical security. The hardware still belongs to the customer.
In practice
A company that has just renewed its servers can move them to a data centre instead of keeping a server room.
The technical and organisational measures that protect systems, data and people from attacks and mistakes. It combines prevention, detection, response and recovery: none of the four is enough on its own.
A facility designed to host servers and network equipment with controlled power, cooling, connectivity and physical security. Its quality drives much of the real availability of a company's systems.
In practice
A server cabinet in an office cannot offer the same power or access guarantees as a data centre.
The country or territory where a company's data is physically stored and processed. It matters in contracts, audits and regulated sectors, and should be documented before signing a cloud service.
In practice
Knowing the data stays in a data centre located in Spain simplifies many compliance conversations.
A fibre connection whose capacity is not shared with other customers, usually with service commitments and priority support. It is chosen when connectivity is critical to operations.
A full physical server assigned to a single customer and hosted in the provider's data centre. It is chosen when predictable performance or exclusive hardware is required.
The procedures and resources used to bring critical systems back after a major incident: fire, serious hardware failure or a cyberattack. It covers who to notify, the recovery order and how results are verified.
In practice
A useful plan is a tested plan: without regular drills it only exists on paper.
The system that translates names such as a website or mail server into IP addresses. A DNS mistake can take down web or email even when the servers themselves are fine.
Recovery capability contracted as a service: the provider keeps replicas of your systems ready to start in its data centre. It avoids duplicating your own hardware for a scenario you hope never to use.
Advanced endpoint protection that blocks known threats and also analyses suspicious behaviour, allowing a compromised device to be isolated. It goes beyond signature-based antivirus.
In practice
If a laptop starts mass-encrypting files, EDR can stop the process and take it off the network.
Any device connected to the corporate network: laptops, desktops, servers or mobiles. They are the most common entry point for incidents, which is why many security controls focus on them.
Automatic switchover to a backup system or line when the primary one stops working. Returning to the primary once it is healthy again is called failback.
In practice
A company with fibre as its primary link and Starlink as backup can keep working if the fibre goes down.
A device or service controlling which traffic may enter and leave the company network. A firewall only adds value when someone maintains its rules, reviews its logs and keeps firmware current.
Configuring a system to shrink its attack surface: disabling unnecessary services, limiting permissions, changing default credentials and closing unused access paths.
A design that keeps a service running even when one component fails, thanks to redundancy and automatic switchover to a healthy element. It does not remove incidents: it shortens how long they are felt.
In practice
If a cluster host goes down, its virtual machines can restart on another node within minutes.
A combination of on-premises or private cloud infrastructure with public cloud services, managed as a single environment. It lets you decide where each workload lives based on cost, performance or compliance.
In practice
The ERP can stay in a private cloud while email and productivity tools run on public services.
An architecture that combines compute, storage and virtualisation in a single set of nodes managed as one unit. It simplifies administration and lets you grow by adding nodes instead of redesigning the platform.
The software layer that shares a physical server's resources between the virtual machines running on it. It makes virtualisation possible and determines how workloads are isolated and prioritised.
A model where you contract infrastructure (CPU, memory, storage and network) and keep control of the operating system and applications. The provider takes care of hardware, power and connectivity.
In practice
Renting a cloud server with 8 vCPUs and 32 GB of RAM to host your own application is IaaS.
Controlling who can access which systems and with what permissions, from onboarding to offboarding. A well-kept directory prevents active accounts for people who have left.
In practice
Offboarding should disable email, VPN and application access on the same day.
A copy that cannot be changed or deleted for a defined period, not even with administrator credentials. It is the strongest defence against ransomware that tries to destroy backups before encrypting data.
A measure of how many read and write operations a storage system can serve each second. It is a useful indicator when a database or ERP feels slow despite having enough CPU and memory.
A structured review of infrastructure, backups, security and processes, delivered as a report of risks and priorities. It helps you decide with evidence before investing.
Delegating all or part of the systems function to an external provider. It is common in companies with no in-house IT team, or when the internal team needs specialist support.
The time data takes to travel to a destination and back. High latency makes applications feel slow even with plenty of bandwidth, and it is decisive for remote desktop and voice.
A general term for any program built to damage, spy on or take control of a system. It covers ransomware, trojans, credential stealers and unauthorised remote access tools.
A model where a provider takes ongoing responsibility for IT infrastructure: monitoring, maintenance, updates and support, under agreed service levels. It replaces the habit of calling only when something breaks.
Sign-in that requires more than a password: a one-time code, a phone prompt or a hardware key. It is one of the highest-impact security measures for the least effort.
In practice
With MFA enabled, a password stolen through phishing is not enough to reach the corporate mailbox.
Microsoft's cloud email, productivity and collaboration suite. Even though the vendor runs the service, the company remains responsible for access, permissions and backups.
Continuous supervision of servers, networks, backups and services to catch problems before users notice them. Its value depends on alerts reaching someone who acts on them.
In practice
A failing disk or an incomplete backup can be spotted days before it becomes an incident.
Splitting the network into separate zones so a problem in one does not spread to the rest. It matters most where office IT, industrial production, cameras and guest devices coexist.
In practice
Isolating shop-floor machinery from the office network limits the blast radius of an incident.
Applying operating system and application security updates on a planned schedule. Most incidents exploit flaws that are already known and fixed by the vendor.
In practice
A monthly calendar with a testing window avoids both the risk of not patching and that of breaking an application.
Messages that impersonate a trusted sender to obtain credentials, data or payments. It is the most common way into a company, countered with email filtering, multi-factor authentication and staff awareness.
A cloud environment whose compute and storage resources are reserved for a single organisation. It gives more control over performance, security and data location than a shared environment.
In practice
A company running a sensitive application can require dedicated resources and know exactly which data centre holds its data.
Cloud services delivered by a provider on infrastructure shared across many customers. It stands out for fast provisioning and elasticity, with less control over the underlying platform.
In practice
It is commonly used for short-lived capacity peaks or for services that do not depend on specific hardware.
A standard cabinet housing servers and network equipment. Space is measured in rack units (U): a typical server occupies 1U to 2U, which makes contracted space easy to calculate.
An attack that encrypts a company's data and demands payment to release it, often after stealing information. Realistic defence combines prevention, early detection and backups the attacker cannot delete.
Duplicating critical elements (power supplies, disks, data links, devices) so that a single failure does not stop the service. It is the foundation of high availability.
In practice
A server with two power supplies on separate circuits keeps running if one of them fails.
Also known as: backup line · radio link · Starlink · SD-WAN
Having more than one internet path — fibre, radio link or satellite — so an outage does not stop operations. Switching between lines can be automatic through failover or SD-WAN.
In practice
A warehouse in a remote industrial estate can combine primary fibre with a radio link or Starlink backup.
Continuous or very frequent copying of data or machines to a second location. It reduces data loss compared with traditional backup, but does not replace copies with historical retention.
The maximum time a system can stay down before the outage becomes unacceptable for the business. It is the target that drives backup, redundancy and recovery design.
In practice
If the ERP has a four-hour RTO, the solution must be able to bring it back into production within that window.
Applications used over the internet on a subscription basis, with no servers to install or maintain. The provider handles updates and availability; the company remains responsible for its data, access and backups.
In practice
An online CRM or a business email suite are SaaS services.
The ability to grow or shrink a system's resources in line with real demand. It avoids paying for idle capacity and absorbs workload peaks without redesigning the infrastructure.
In practice
A company with a seasonal campaign can add capacity for three months and then return to its usual sizing.
A single point of contact where users report incidents and requests, with logging, prioritisation and follow-up. It shows what fails most, how long fixes take and where to invest.
A platform that centralises logs from servers, network and applications to correlate them and raise security alerts. It makes post-incident investigation far easier.
A documented commitment on service levels: support hours, response times and availability targets. Always check what is measured, how it is calculated and what is excluded.
In practice
A one-hour response SLA is not the same as a one-hour resolution commitment.
A point-in-time image of a virtual machine or volume that allows a quick rollback. Very handy before an update, but it is not a backup: it lives on the same system.
The team and processes dedicated to continuously monitoring, detecting and responding to security incidents. Its value lies in fast reaction, not just in raising alerts.
Also known as: IP address · public IP · private IP
A public address that does not change and stably identifies a company's connection. It is needed to publish services, link sites over VPN or restrict access by source.
The disks and systems that hold company data. The chosen technology (spinning disk, SSD or NVMe) and its design shape application speed and how long a restore takes.
Equipment that keeps power flowing during an outage, buying time for backup systems to start or for servers to shut down cleanly. It is the first line of electrical protection in any server room.
The percentage of time a service stays operational within a period. Its opposite is downtime, and both must be read alongside the measurement window: 99.9% a year still allows almost nine hours of outage.
A workstation that runs in the data centre and is reached from any device. It centralises data and updates and enables remote work without information leaving the controlled environment.
A logical server with its own operating system running on hardware shared with other machines. It can be resized, cloned or moved to another host without reinstalling anything.
In practice
Adding memory to a virtual machine usually takes minutes, not a hardware purchase.
Technology that runs several logical servers on the same physical machine. It reduces the number of boxes needed, simplifies backups and speeds up recovery after a hardware failure.
In practice
Four ageing servers can become four virtual machines on two modern hosts in high availability.
Logically separates groups of devices within the same physical network infrastructure. It lets offices, production and guest Wi-Fi have different access without duplicating cabling.
The two most widespread enterprise virtualisation platforms. Both consolidate servers, move virtual machines between hosts and automate backups, differing mainly in licensing and management tooling.
An encrypted connection that lets staff reach company resources from outside the office as if they were on site. It should be paired with multi-factor authentication and least-privilege access.
A weakness in a system, configuration or process that an attacker can exploit. Identifying and prioritising them by real risk works better than trying to fix everything at once.
An evolution of EDR that correlates signals from several sources — endpoints, servers, email, network or identity — to spot attacks that would go unnoticed if each system were analysed alone.
A security approach that does not trust a connection simply because it comes from the internal network. Every access is verified against identity, device and context, granting the least privilege needed.