Security readiness assessment

Frame a cybersecurity readiness conversation without sharing sensitive incident details.

Provide high-level information about your environment, controls, business drivers, and desired outcome. This form is for planning—not emergency incident response.

Security readiness assessment

Tell us what you know about the project.

High-level estimates are welcome. The details below help DSE prepare the right specialists, questions, and next step for the first conversation.

Keep sensitive details out of this form. Do not include passwords, alarm or access codes, vault combinations, financial account data, camera links, exact vulnerabilities, medical information, confidential plans, or security logs. DSE can arrange a safer exchange after the first conversation.

1 About you and the location

Fields marked are required.

Your name

Business email

Phone number

Required only when phone is your preferred follow-up method.

Preferred follow-up

Company or organization

Role or department

Relationship with DSE

Best time to reach you

Project city, state, and ZIP

A city and ZIP are enough for the first conversation; do not include secure facility details.

2 Your environment and scope

High-level estimates are useful; choose “not sure” where available.

Are you reporting a suspected active security incident?

Do not send incident indicators, credentials, vulnerabilities, logs, or compromised-system details through this form.

Security goals to include

Risk or readiness assessment Identity and multi-factor authentication Endpoint detection and protection Email and collaboration security Backup and recovery readiness Security awareness and phishing testing Vulnerability management Policies, governance, and roadmap

Primary business driver

Approximate user count

Approximate endpoint count

Primary identity or email platform

Multi-factor authentication coverage

Operating system and application patching

Managed endpoint protection

Protected backups

Tested recovery process

Security awareness training

Relevant compliance, customer, or insurance requirements

3 Timing, priorities, and next step

Number of locations

Project stage

Target timeline

Planning budget

Optional. A range helps DSE recommend a realistic next step.

What would a successful outcome look like?

Anything else that would help us prepare?

Do not include passwords, alarm or access codes, vault combinations, financial account data, camera links, vulnerabilities, medical information, or confidential plans.

I understand DSE will use these details to respond to this request.

Submitting creates a request for DSE to review; it does not create an emergency service ticket.