Aber Systems

~/infrastructure

IT infrastructure

Networks, servers, cloud services, backups and the security basics every organisation needs: set up deliberately, written down, and handed over in a state that someone else could understand.

Scope
Networks, servers, cloud setup, backups and security basics.
Starts with
An audit of what you have: devices, services, accounts and access.
Runs as
A written plan, carried out in an agreed order with planned interruptions.
Ends with
A working setup, a diagram of it and notes on how to recover it.

01 Areas of work

Five foundations and the paperwork that holds them together

Infrastructure is invisible when it works and very visible when it does not. Each area below can be handled on its own, but they are designed together so the parts do not contradict each other.

A / networks

Networks

Wired and wireless networks planned for the space and for the number of people and devices using them.

  • Router, firewall and switch configuration
  • Wi-Fi coverage with a separate guest network
  • Segments for devices that should not mix
  • Remote access for staff through a VPN

B / servers

Servers

Physical or virtual servers installed, configured and kept tidy, with a clear record of what runs where.

  • Operating system installation and hardening
  • File sharing with sensible permissions
  • Virtual machines and application hosting
  • Storage layout and health checks

C / cloud

Cloud setup

Cloud accounts and services configured on purpose: who can access what, where data lives and how it is recovered.

  • Business email and shared file storage
  • User accounts, groups and sign-in rules
  • Hosting environments for web applications
  • Migration from local servers or between providers

D / backups

Backups

A backup is only useful if the restore works. We configure the first and test the second.

  • What is backed up, how often and for how long, agreed with you
  • A local copy and a copy kept off-site
  • Encryption of backup data
  • Restore tests and a written recovery procedure

E / security

Security basics

The unglamorous measures that prevent most everyday incidents, applied consistently instead of occasionally.

  • Multi-factor authentication on key accounts
  • A password manager in place of shared notes
  • A routine for updates and patches
  • Device encryption and screen-lock rules
  • A joiner and leaver process for accounts

F / documentation

Documentation

Everything we set up is written down, so the knowledge does not live in one person's head — ours included.

  • Network diagram and device inventory
  • Where credentials are kept and who holds them
  • Recovery steps for the important systems
  • Renewals to watch: domains, certificates, subscriptions

02 Layout

A typical small-office layout

One example of how the pieces connect. The principle behind it is separation: guests, staff devices, servers and backups each get their own place, and the connections between them are deliberate.

Typical small-office network layout Outside the office: remote staff reach the internet connection over a VPN; cloud services and an off-site backup copy also sit outside. Inside the local network: the internet connection enters through a firewall and router, which serves a separated guest Wi-Fi and a switch. The switch connects staff devices and a server. The server is copied to a local backup, which is copied to the off-site backup. Monitoring checks the firewall, the server and the backup jobs. OUTSIDE THE OFFICE LOCAL NETWORK VPN Remote staff laptops at home or away Internet provider connection Cloud services email, files, hosting Off-site backup second copy, encrypted Guest Wi-Fi internet only Firewall / router rules, VPN endpoint Monitoring health, alerts, backup jobs Staff devices wired + staff Wi-Fi Switch separated segments Server / storage files, applications Local backup fast restore connection checked by monitoring
Fig. 2 — Example layout. Your own diagram is drawn during the audit and updated when anything changes. Scroll sideways to see the whole drawing.

Edge

One way in

Traffic from outside passes a firewall with rules somebody chose, not the defaults the device shipped with.

Inside

Separated segments

Guests, staff devices and servers sit on separate segments, so one compromised device does not see everything.

Copies

Two backups

A local copy for quick restores and an off-site copy for the day the office itself is the problem.

Watch

Monitoring

Automatic checks on the firewall, the server and the backup jobs, so a failure is noticed when it happens.

03 Process

How an infrastructure job runs

Whether it is a new office, a move to the cloud or tidying up a setup that grew by itself, the order of work is the same.

  1. Audit

    We list what exists: devices, services, accounts, who has access to what, and how it is all connected.

    You receiveAn inventory and a list of risks, ordered by how much they matter.

  2. Plan

    We propose what to change, in what order and why, including which steps need an interruption.

    You receiveA written plan and an equipment list, if anything needs buying.

  3. Implement

    Changes are carried out at agreed times, with a way back prepared for anything that could go wrong.

    You receiveA working setup, tested against the plan.

  4. Document

    The result is written down and walked through with whoever will be responsible for it.

    You receiveA diagram, recovery notes and the credentials.

Plans written so you can check them

Configuration is detail, but the decisions behind it are yours to make. Each plan is summarised in plain terms, like the three examples in the panel.

  • Every line states a decision, not a product name
  • Choices that depend on you are marked as such
  • The same document is updated when the setup changes

# backups: agreed with you, written in plain terms

whatshared files, databases, mailboxes, server configuration

copiesone local, one off-site

encryptionon, for both copies

scheduleset by how much work you can afford to lose

retentionset by how far back you may need to go

restoretested, with the steps written down

# network: separated by purpose

staffworkstations, laptops, phones

serversfile storage, applications

guestsinternet only, no route to internal systems

devicesprinters, cameras, anything that should not see everything

remoteVPN for staff working elsewhere

firewallclosed by default, opened for stated reasons

# accounts and access

accountsone per person, no shared logins

mfaon for email, admin and remote access

adminseparate admin accounts, used only when needed

joinersaccess granted by role, from a checklist

leaversaccess removed as part of the leaving process

passwordskept in a password manager, not in a spreadsheet

04 Questions

Common questions about infrastructure work

If yours is not here, ask it directly: contact@vatutuexa.site.

Do we need our own server, or should everything be in the cloud?

It depends on your applications, your internet connection and where your data has to be kept. Part of the audit is laying out the options with their trade-offs, so the decision is yours and it is an informed one.

Can you take over a setup that nobody documented?

Yes. That is the usual starting point. The audit produces the inventory and the diagram that were missing, and from then on changes are recorded.

Will there be downtime while you work?

Some changes need a short interruption. Those are identified in the plan, scheduled for a time that suits you, and prepared with a way back in case something does not go as expected.

Who buys the hardware?

We specify what is needed and why, in a list you can purchase from. How the equipment is bought is agreed in the proposal.

How do we know the backups work?

Because a restore is tested and the result is recorded. A backup that has never been restored is an assumption, not a backup.

Is this a security audit or a compliance certification?

No. This service covers practical security basics. It is not a formal audit, a penetration test or a certification. If your situation calls for one of those, we will say so and help you prepare for it.

05 Next step

Start with what you have today.

A rough description is enough: how many people, what kind of premises, which services you rely on, and what worries you most.

aber@systems: ~/contact

mail contact@vatutuexa.site

peoplehow many, and where they work from

todayservers, cloud services and network you have now

worrywhat would hurt most if it stopped working

timingan office move, a renewal, any date that matters