RESOURCES / SECURITY BASICS

The fundamentals
do the heavy lifting.

Effective security begins with consistent practices, clear ownership, and systems that are reviewed over time.

FIVE FOUNDATIONS

Get the basics right.

The depth changes with the business; the underlying principles remain the same.

01

Secure configuration

Start with known baselines, limited privileges, sensible defaults, and less unnecessary exposure.

02

Patch discipline

Use predictable update cycles, validation, and controlled exceptions to reduce avoidable risk.

03

Identity & access

Protect accounts with strong authentication, multi-factor authentication, and access that reflects each role.

04

Recovery readiness

Identify critical data, define retention, and validate that restores can work when needed.

05

Visibility & review

Monitor meaningful signals, document decisions, and revisit controls as the environment changes.

UNDERSTAND THE WHY

What good practice looks like.

Useful questions a business owner can take into a discussion with any IT provider.

01 / FOUNDATION

Secure configuration

A system can work while carrying settings nobody intended to leave in place. Secure baselines, sensible defaults, and limited administrative access reduce unnecessary exposure.

A useful question: Ask whether new computers are configured to a common standard and whether old services or accounts are still needed.

Explore system hardening
02 / FOUNDATION

Patch discipline

Updates address known issues, but the best schedule should account for the work those systems perform. Predictable cycles and validation are more dependable than sporadic catch-up.

A useful question: Know who checks update status and how exceptions are recorded when a system cannot be updated immediately.

Explore patch management
03 / FOUNDATION

Identity & access

A person should have access to the systems their role requires, with strong authentication and MFA where appropriate. Access should change when roles change.

A useful question: Review shared accounts, former staff access, administrative privileges, and the recovery options on important accounts.

Explore endpoint & access controls
04 / FOUNDATION

Recovery readiness

A backup job reporting success is one part of protection. Coverage, secure storage, retention, recovery order, and restore verification determine whether the business can resume work.

A useful question: Identify the data and systems you would need first, then ask when they were last restored in a test.

Explore backup & recovery
05 / FOUNDATION

Visibility & review

Health checks, patch status, backup results, and meaningful alerts help people act before a small problem becomes a larger interruption.

A useful question: Decide who reviews these signals, how often, and what happens when a finding needs action.

Explore monitoring & reporting

THE CONTINUING WORK

Consistency needs ownership.

No single product makes these practices permanent. Someone must know the standard, document exceptions, review the results, and adjust the work as the business changes. That is why Summit defines scope and cadence before ongoing services begin.

Learn how Summit approaches the work

TAKE IT FURTHER

Use a working reference.