Intake Forms for Cybersecurity Consulting: Assessing the Threat Landscape Before the Engagement Begins

By Daniel Akselrod · July 2026

A cybersecurity engagement that begins without a structured intake is an engagement that starts blind. The consultant walks in, asks a few broad questions about what keeps the client up at night, and then spends the first two weeks of a six-week contract just figuring out what the environment actually looks like. That is two weeks of billable time spent on discovery that should have happened in a 45-minute intake conversation. The right intake form does not just collect contact information and a project description. It maps the entire threat landscape before a single scan runs, before a single policy document gets reviewed, before anyone touches a firewall rule.

The Infrastructure Picture: What Are We Actually Protecting?

Every cybersecurity engagement starts with the same fundamental question, and most clients cannot answer it cleanly: what does your environment look like? The intake form needs to capture network topology at a high level, not a full Visio diagram, but enough to understand whether you are looking at a flat network with 30 endpoints and a single router, or a segmented enterprise with multiple VLANs, DMZs, and site-to-site VPN tunnels connecting four branch offices. The distinction between on-premises infrastructure, cloud-native deployments, and hybrid environments changes everything about how the engagement gets scoped. A company running entirely on AWS with Infrastructure as Code has a fundamentally different attack surface than a company with a server closet, a SonicWall firewall that has not been updated since 2019, and a domain controller running Windows Server 2012 R2.

Cloud provider details matter here too. AWS, Azure, and GCP each have different shared responsibility models, different native security tooling, and different misconfigurations that show up in assessments. A client running a multi-cloud environment with workloads split between Azure for their Microsoft stack and AWS for their web applications introduces complexity that a single-cloud client does not. The intake form should capture which providers are in use, whether Infrastructure as Code tools like Terraform or CloudFormation are deployed, and whether the client has ever run a cloud security posture assessment. Most have not. That is itself a finding.

Compliance Is Not Optional, and Neither Is Asking About It

The regulatory landscape surrounding a client determines the minimum bar for the engagement. A healthcare organization subject to HIPAA has encryption requirements, access logging mandates, and breach notification timelines that shape the entire assessment. A company processing credit card transactions falls under PCI-DSS, and the specific Self-Assessment Questionnaire type they need to complete depends on their transaction volume and processing method. Defense contractors pursuing CMMC Level 2 certification need every one of 110 NIST 800-171 practices documented and implemented. A SaaS company with enterprise customers is going to need SOC 2 Type II, which means the controls are not just in place but have been operating effectively for a sustained period.

State privacy laws add another layer. California's CCPA and CPRA, Virginia's CDPA, Colorado's CPA, Connecticut's CTDPA, and the growing list of state-level data protection statutes each carry their own requirements around data inventory, consumer rights, and breach notification. The intake form should capture every regulatory framework the client believes applies to them, plus a free-text field for any they are unsure about. That uncertainty field is often where the most important information surfaces. A client who writes "we think we might need to worry about CMMC because our customer is a defense contractor" just told you something their compliance team has been quietly ignoring for months.

Incident History: The Scars That Shape the Engagement

No client walks into a cybersecurity engagement without history, even if they think they do. The intake form needs to ask directly about prior breaches, ransomware events, business email compromise incidents, successful phishing campaigns, and any data exposure events, whether reported externally or handled internally. The way the question is framed matters. Asking "have you experienced any security incidents?" gets a reflexive "no" from most small and mid-sized businesses. Asking "has any employee ever clicked a phishing link, had their email account compromised, or reported suspicious activity on their workstation?" gets a much more honest answer, usually followed by a story about that time in 2023 when the controller almost wired $50,000 to a spoofed vendor.

Phishing success rates, if the client tracks them, are one of the most telling metrics on the entire intake form. A company that runs quarterly phishing simulations and has driven their click rate from 28 percent down to 4 percent over two years is in a completely different posture than a company that has never tested. Prior ransomware events are critical because they reveal both the technical vulnerabilities that allowed the attack and the organizational response capabilities. Did they have backups? Were the backups airgapped? Did they pay the ransom? How long was the recovery? Each answer shapes what the consultant focuses on during the engagement.

Access Controls: The Keys to the Kingdom

Access control documentation is where the gap between what a company says they do and what they actually do becomes most visible. The intake form should capture multi-factor authentication status across the organization: is MFA enforced on all accounts, only on privileged accounts, only on VPN, or not at all? Password policy details matter too, specifically minimum length, complexity requirements, rotation frequency, and whether the organization uses a password manager. The honest answer from most small businesses is that there is a written password policy in an employee handbook that nobody has read since 2021, and actual practice varies wildly by department.

Privileged account management is its own section on the form. How many domain admin accounts exist? Are there shared admin credentials? Who has root access to the Linux servers? Is there a formal process for provisioning and deprovisioning access when employees join, change roles, or leave the company? The answer to that last question is almost always "sort of." Onboarding usually works because HR has a checklist. Offboarding is where access lingers. Former employees with active VPN credentials six months after termination is not a hypothetical finding in most assessments. It is one of the most common ones.

Vendor and Third-Party Risk: The Blast Radius Beyond Your Walls

Modern organizations do not operate in isolation. A company with 50 employees might have 30 SaaS subscriptions, each one representing a potential data exposure point. The intake form needs to capture the client's awareness of their SaaS footprint, any existing vendor risk assessment process, data sharing agreements with third parties, and whether critical business functions depend on vendors that the client has never evaluated from a security perspective. The question "which third-party vendors have access to your customer data?" produces either a confident, documented answer or a long pause followed by "I would have to check." That pause tells the consultant more than a formal vendor risk register would.

Supply chain risk extends beyond SaaS. If the client uses managed service providers for IT support, those MSPs typically have broad administrative access to the environment. If the MSP gets compromised, the client gets compromised. This is not theoretical. The Kaseya and SolarWinds incidents demonstrated exactly how supply chain attacks cascade through managed service relationships. The intake form should capture who manages the client's IT infrastructure, what level of access they have, and whether that access has ever been formally scoped or reviewed.

People and Training: The Human Firewall

Employee count and organizational structure determine the human attack surface. A 500-person company with a dedicated IT security team of three is in a different position than a 500-person company where the "IT department" is one system administrator who also manages the phone system. The intake form should capture total employee count, number of IT staff, whether any staff hold security-specific roles, and the history of security awareness training. Has the company ever conducted formal training? How recently? Was it a one-time onboarding video or an ongoing program with simulated phishing, interactive modules, and measurable outcomes? Companies that check the "yes, we do security training" box often mean they showed a 15-minute video during orientation three years ago. That is not training. That is a liability shield, and not a very good one.

Scope of Engagement: What Are You Actually Hiring Us to Do?

This is where ambiguity kills engagements. Cybersecurity consulting covers a vast range of services, and clients often use terms loosely. "We want a security audit" might mean a penetration test, a vulnerability assessment, a compliance gap analysis, a policy review, or all of the above. The intake form needs to present distinct engagement types and let the client indicate which ones they are seeking: penetration testing with clearly defined scope boundaries, vulnerability scanning and assessment, compliance readiness evaluation against a specific framework, incident response retainer or active incident investigation, ongoing managed security services, security policy development, or tabletop exercises and disaster recovery planning. Each of these is a different engagement with a different timeline, different deliverables, and a different price. A client who thinks they are buying a two-week pen test but actually needs a three-month compliance readiness program is going to be disappointed when the statement of work arrives, unless the intake conversation clarified the scope before anyone started drafting proposals.

The Vulnerabilities the Client Does Not Know They Have

Here is the part that makes cybersecurity intake different from almost every other professional services intake. In most fields, the client knows what their problem is. They have a leaky roof, an employment dispute, a tax filing deadline. In cybersecurity, the client frequently does not know what their problem is, and the intake form is designed to reveal exactly that. A client who writes "we use MFA everywhere" and then, three fields later, admits they have no process for deprovisioning former employees just contradicted themselves without realizing it. A client who reports no prior security incidents but also reports that they have never conducted a phishing simulation is not incident-free. They are detection-free. A company that lists eight SaaS vendors with access to customer data but has no vendor risk assessment process does not have a vendor management program. They have a collection of trust assumptions that have never been tested.

The structured intake form surfaces these gaps mechanically. It does not require the consultant to ask the right follow-up question in real time. It does not depend on the client volunteering information they do not realize is important. The form walks through every domain, methodically, and the pattern of answers tells a story the client did not know they were telling. That story is the actual starting point of the engagement. Everything the consultant does from that point forward is informed by what the intake revealed, and what the client's answers revealed about themselves. That is the difference between a cybersecurity engagement that begins with clarity and one that begins with guesswork. The right intake form eliminates the guesswork on day one.

Ready to Upgrade Your Intake Process?

Professional fillable PDF forms — instant download, no monthly fees.

Browse All Forms View Bundles

Not ready to buy? Download our free Universal Intake Form — a fillable PDF you can use today, no purchase needed.