Skip to main content

About Kessel Security Analytics

Advisory-only cybersecurity and compliance guidance for small organizations—designed to reduce uncertainty, avoid conflicts of interest, and keep owners in control.

Why this advisory exists

Many small organizations feel trapped between two extremes: ignoring risk entirely or being told they need an enterprise-grade security and compliance program.

Most owners don’t need more tools or jargon. They need clear judgment about what applies to their business, what actually matters, and what can reasonably wait.

This advisory work exists to provide that clarity—without pressure, upselling, or loss of control.

Experience that shapes the work

This approach is informed by more than two decades working in cybersecurity and risk-related roles, including time in large, highly regulated environments such as Fortune 5 organizations.

Much of that experience comes from healthcare, human services, and complex operational settings where compliance expectations, technical reality, and human behavior often collide.

The focus here is not theory or perfection. It is practical judgment—helping small teams avoid mistakes that larger organizations have already learned the hard way.

How risk is approached

Risk tends to concentrate in predictable places for small organizations: accounts and access, email and endpoints, backups and recovery, vendor dependencies, and the operational “what happens if” scenarios.

The goal is not a perfect score or exhaustive checklist. The goal is fewer surprises and calmer decisions—without overbuilding or overspending.

Why advisory-only matters

Keeping advisory separate from implementation protects clarity and trust. I do not log into systems, perform remediation, or take operational control.

Instead, I assess, explain, and prioritize. Your internal team or IT provider implements changes on your timeline.

Professional and ethical boundaries

This advisory work is informed by formal cybersecurity training and professional obligations, including adherence to the ISC² Code of Ethics (CISSP). In practical terms, that means clear constraints designed to protect clients and avoid conflicts of interest.

  • • I do not resell security tools, software, or services
  • • I do not accept commissions, referral fees, or vendor incentives
  • • I do not monetize, reuse, or retain client information beyond advisory context
  • • I do not log into client systems or maintain operational access
  • • Client discussions and materials remain confidential and advisory-only

These boundaries exist to keep advice objective, preserve trust, and ensure recommendations are based solely on the client’s best interest.

Optional: how the advisory is organized

You don’t need to learn a framework to work together. For those who prefer structure, the advisory work is organized into four practical areas.

Clarity

Understanding obligations, expectations, and gray areas in plain language.

Stability

Strengthening everyday security hygiene so common issues are less likely.

Vendor & Cloud Risk

Clarifying responsibilities and dependencies across the tools you rely on.

Resilience

Preparing for outages and disruptions so recovery is faster and calmer.

If this approach resonates

The simplest next step is a short, plain-language conversation. You can ask questions, describe your situation, and decide whether advisory support makes sense.

Start a Conversation