MonolithTechnologies Limited
Security

A security baseline every small engineering team can adopt this quarter

Seven controls that remove the most common risks for small teams: MFA, secrets handling, least privilege, patching, tested backups, encryption and logging.

Abraham Olagunju

27 Oct 2026 · 2 min read

A security baseline every small engineering team can adopt this quarter

Security work feels endless, which is why small teams often postpone it. The way out is a short baseline: a handful of controls that remove the most common ways things go wrong, applied consistently. These are the ones we start with on almost every engagement.

1. Turn on multi-factor authentication everywhere

Email, source control, cloud console, domain registrar, payment dashboards. Compromised credentials remain the most common way in, and MFA stops most of those attempts. Prefer authenticator apps or hardware keys over SMS where you can.

2. Keep secrets out of code

  • Store API keys and database credentials in environment variables or a secrets manager.

  • Never commit them. Add secret scanning to your repository so a mistake is caught before it ships.

  • Use separate keys per environment and rotate them when people leave or a key is exposed.

  • Use restricted keys in the browser and secret keys only on the server.

3. Give people the access they need, and no more

Use named accounts rather than shared logins, and review who has access to production every quarter. When someone changes role or leaves, remove access the same day.

4. Patch dependencies on a schedule

Most applications are mostly other people's code. Enable automated dependency alerts, review updates weekly, and treat known critical vulnerabilities as urgent. Pin versions and keep a lockfile so builds are repeatable.

5. Back up, and test the restore

A backup you have never restored is a hope, not a plan. Automate backups of databases and uploaded files, keep copies in a separate account or region, and practise a restore at least twice a year.

6. Encrypt and validate

  • Serve everything over HTTPS and redirect plain HTTP.

  • Validate and sanitise all input on the server, whatever the client does.

  • Collect only the personal data you need and know where it is stored. In Nigeria, that includes your obligations under the Nigeria Data Protection Act.

7. Log, alert and write the first page of an incident plan

You cannot respond to what you cannot see. Log authentication events and administrative actions, alert on unusual activity, and write down who does what in the first hour of an incident, including who talks to customers.

0 Comments

Loading comments…

Related articles