B2B SaaS Security Posture Discovery Brief

Role: Senior Cybersecurity Sales Engineer and Compliance Discovery Strategist.

Context

• Prospect Organization: {{prospect_company}}
• Relevant Compliance Framework: {{target_compliance_standard}}
• Existing Security Stack: {{vendor_security_environment}}
• Security Buyer Persona: {{security_decision_maker_title}}
• Data Handling Scope: {{regulated_data_profile}}

Task

Construct a pre-call Security Discovery Brief for {{prospect_company}} that maps vulnerabilities in {{vendor_security_environment}} against {{target_compliance_standard}} mandates to guide consultative qualification calls.

Method

1. Review {{target_compliance_standard}} controls applicable to {{regulated_data_profile}}.
2. Identify known integration frictions between modern cloud SaaS and {{vendor_security_environment}}.
3. Formulate persona-specific discovery questions tailored to the authority level of {{security_decision_maker_title}}.
4. Map potential data governance exposure points that arise from unmanaged software sprawl.
5. Draft positioning statements that address security audit anxiety without generating vendor defensiveness.
6. Outline a mutual security review timeline required to protect contract signing dates.
7. Detail two critical disqualification criteria that signal insurmountable technical risk.

Constraints

• MUST address compliance obligations under {{target_compliance_standard}} explicitly.
• MUST NOT provide binding legal or compliance guarantees.
• Must present discovery questions in ascending order of technical invasiveness.
• Must maintain a non-adversarial, collaborative posture throughout all discovery prompts.

Output format

• Executive Context (2 bullet points summarizing compliance landscape)
• Regulatory Friction Analysis (max 100 words)
• Targeted Discovery Prompts (5 categorized questions: Architecture, Access, Compliance, Incident Response, Governance)
• Red Flag Triggers (2 clear disqualification criteria)
• Mutual Security Validation Roadmap (3 concise phases)

Self-review

• Check that all 5 discovery prompts directly engage {{security_decision_maker_title}}.
• Confirm that the implications of {{regulated_data_profile}} are accurately assessed.
• Verify no legal or indemnification promises are stated in the brief.