Mohamed Sharaf

Next year’s security plan: one thing a month

Big security programmes stall. Twelve small, finished improvements beat one big plan that never starts.

· 1 min read

Every January I see big security plans. By March most have stalled. Here’s a plan that small teams actually finish: one improvement a month, done properly.

  1. January: MFA on every account that supports it.
  2. February: a password manager for everyone.
  3. March: list your assets: devices, servers, cloud services, domains.
  4. April: automatic updates everywhere; a plan for what can’t update.
  5. May: backups with one copy that can’t be deleted; test a restore.
  6. June: remove admin rights from daily accounts.
  7. July: close anything exposed to the internet that doesn’t need to be.
  8. August: central logs, kept for at least 90 days.
  9. September: SPF, DKIM and DMARC on your email domain.
  10. October: a one-page incident plan, and who to call.
  11. November: review who has access to what; remove the extras.
  12. December: a small test, such as a phishing exercise or an outside scan, and next year’s list.

Finished small things add up. Happy new year.

ShareWhatsAppLinkedInXTelegramFacebook