DwCyber

An arch of six labeled stones, DevOps, Cloud, Architecture, Security, Identity and AI advisory, held by a teal keystone labeled David

Hover a stone.

The cloud, AI and security expert who holds the rest together.

Adviser and hands-on engineer for cloud, DevOps, security, identity and AI. One person who sees your whole stack, turns an idea into a real system, builds and maintains it, or guides your team to the finish.

Email David or write to contact@dwcyber.com

Where you are

Something broken, or something new to build: you do not need to know which kind it is. Pick the closest situation; see what changes.

What changes

Scoped with you, a first working version secured from day one, then maintained by me or handed to your team.

Stones involved: Architecture, DevOps, Security

Watch: the idea raises an app, data and a pipeline, then a ring secures them.

What changes

A written architecture and security position that survives an outside reviewer, with the expensive fixes done before they ask.

Stones involved: Architecture, Security, Cloud, DevOps

Watch: the costly findings are fixed and land on your position before the outside reviewer scans.

What changes

A migration with a rollback for every step and a bill estimated before the move.

Stones involved: Cloud, DevOps, Architecture

Watch: containers cross one at a time, and each leaves its outline behind as the way back.

What changes

Contained first. Then a plain account of what happened, and the access and monitoring changes that keep it from repeating.

Stones involved: Security, Identity

Watch: the spread is stopped, the compromised connection is cut, then monitoring is added.

What changes

Gaps closed in order of risk, controls that exist in the systems, and evidence ready to copy and paste into the next one.

Stones involved: Security, Identity, Architecture, DevOps

Watch: the riskiest gaps turn green first, and each control lights as its evidence arrives.

What changes

Rules for what may leave the company, tools chosen on evidence, and automation built so it does not leak what matters.

Stones involved: AI advisory, Security, Identity

Watch: green (safe) data passes the gate to the AI tools; red (sensitive) data stops at the gate.

How an engagement can run

Every engagement is different. This is the usual shape, and I adapt it to you.

  1. We talk.

    Tell me what is going on, in whatever words you have. No form, no pitch.

  2. I scope it.

    I work out what you actually need and tell you plainly, including what you can leave alone.

  3. We plan it together.

    We decide what I handle and what goes to your own teams. All of it, none of it, or any mix, and it can change as we go.

  4. Then we follow up.

    We close it out and I step back, or we keep going: more work, another area, a standing arrangement. Your call.

    What you receive

    • A report where every finding says what was observed and where.
    • Working systems, pipelines and runbooks you own.
    • Decision papers that argue both options fairly, including the one that is less work for me.
    • A log of every change made in your environment, written before it ran, with its rollback.

The same arch, with the keystone in place.

Place the keystone.

One email starts it. Say what is going on; I will tell you what I would do first.

David Winston, CISSP and CISM, CISO and DPO, with years of experience in both small and large setups.

Not technical? You describe the business situation; I do the translation.

Developers, or only an idea? With a team, I work alongside them. With only an idea, I build and maintain it.

Hebrew? Natively, and English.

contact@dwcyber.com