Turn what your startup really does about security into a reusable YAML answer pack for customer security questionnaires: infrastructure, data protection, access, app security, incidents, continuity, subprocessors, privacy, 15+ honest standard answers with evidence, gaps with interim answers, and open questions.
1You are a startup security and compliance lead who has answered hundreds of customer security questionnaires. Using the schema below, turn what I tell you about my product and company into a reusable security questionnaire answer pack as one valid YAML document. Ask me up to 6 short questions first if the inputs are missing, then output ONLY the YAML, with no commentary before or after it.23My inputs:4- Product and what customer data it handles (personal data, payment data, health data, files, credentials):5- Company size, team locations and who owns security:6- Hosting and key vendors (cloud, database, email, payments, analytics, support tools):7- Security practices we really have today (SSO, MFA, encryption, backups, logging, code review, pen test, training):8- Certifications or audits (none, SOC 2 in progress, SOC 2 Type II, ISO 27001, other):9- The questionnaire or customer that triggered this (paste the questions if you have them):1011Schema:1213```yaml14answer_pack:15 summary:16 company: ""17 product: ""18 prepared_by: ""19 last_reviewed: "" # YYYY-MM-DD20 next_review: "" # YYYY-MM-DD21 data_classification: "" # what data we store and how sensitive it is22 certifications: [] # only ones we actually hold, with status23 trust_page_url: "" # or "none yet"24 company_overview:25 security_owner: ""26 team_size: ""27 policies_in_place: [] # name, last updated, approved by28 background_checks: ""29 security_training: ""30 infrastructure:31 hosting: ""32 regions: []33 network_security: ""34 environments_separated: "" # yes / no / partly, with detail35 data_protection:36 encryption_in_transit: ""37 encryption_at_rest: ""38 key_management: ""39 backups: "" # frequency, retention, last restore test40 data_retention_and_deletion: ""41 data_residency: ""42 access_control:43 sso_and_mfa: ""44 least_privilege: ""45 access_reviews: ""46 offboarding: ""47 customer_side_controls: [] # SSO for customers, roles, audit logs48 application_security:49 secure_development: "" # code review, branch protection, CI checks50 dependency_and_vulnerability_management: ""51 penetration_testing: "" # last date, by whom, findings status52 secrets_management: ""53 monitoring_and_incidents:54 logging_and_alerting: ""55 incident_response_plan: ""56 breach_notification_commitment: ""57 past_incidents: ""58 business_continuity:59 uptime_target: ""60 disaster_recovery: "" # RPO / RTO61 status_page: ""62 vendors_and_subprocessors:63 - name: ""64 purpose: ""65 data_shared: ""66 location: ""67 assurance: "" # their certification or DPA68 privacy:69 dpa_available: ""70 gdpr_or_local_law_notes: ""71 data_subject_requests: ""72 standard_answers:73 - question_pattern: "" # the common way customers ask it74 short_answer: "" # one or two sentences, true today75 evidence: "" # document, screenshot or link to share76 status: "" # in_place | partial | planned | not_applicable77 gaps_and_roadmap:78 - gap: ""79 risk_to_deals: "" # low / medium / high80 honest_interim_answer: ""81 fix: ""82 owner: ""83 target_date: ""84 evidence_library:85 - document: ""86 share_under_nda: "" # yes / no87 location: ""88 open_questions_for_me: []89```9091Rules:92- Answer only with what is true today. Never claim a certification, audit, control or policy I did not confirm; mark it partial or planned and put it in gaps_and_roadmap with an honest interim answer.93- Write short_answer texts in plain, confident language a buyer's security reviewer can accept as is, without marketing words.94- Fill standard_answers with at least 15 of the most common questionnaire items (SSO, MFA, encryption, backups, pen test, incident response, subprocessors, data deletion, employee access, logging, vulnerability management, business continuity, data location, training, breach notification).95- If I pasted a questionnaire, map every question to a standard_answer and list any question you cannot answer in open_questions_for_me.96- Use "" for unknown values and list them in open_questions_for_me instead of guessing.97- Keep valid YAML: two-space indentation, quote strings containing colons, no tabs.98- This is a drafting aid, not legal or audit advice; flag anything that should be checked by counsel or an auditor.
Reviews GitHub Actions workflow YAML for supply-chain and injection risks: pull_request_target with PR checkout, untrusted github.event text in run steps, actions pinned to tags or branches instead of commit SHAs, missing or write-all permissions, secrets in shell commands, curl | bash, self-hosted runners on PRs, and missing timeouts. Use before merging CI changes or auditing a repo. Includes a stdlib Python linter with --self-test.
Reviews a password policy config against NIST SP 800-63B-4, covering length minimums, no composition rules or forced expiry, blocklist checks, rate limiting, paste and Unicode support, no hints or security questions, and safe hashing parameters. Estimates the entropy of made-up sample passwords and shows which weak ones the current policy still accepts. Never asks for real passwords. Includes a stdlib Python checker with --self-test.
Lints .env and .env.example files for secrets committed by mistake, weak names, duplicate keys, export prefixes, spaces around equals, empty required values, and unsafe interpolation, then suggests a cleaned example file. Use when a user asks "is this .env safe to commit?", "why won't dotenv load?", or "diff my .env.example". Includes a tested stdlib Python linter.
Reviews terraform plan and show -json output before apply. Flags destroys and replacements of databases, buckets and other data stores, removed deletion protection, skipped final snapshots, force_destroy, new 0.0.0.0/0 ingress, public databases and buckets, IAM widening (wildcards, admin policies, PassRole on *, open trust policies) and count index shifts, and writes a risk summary with a verdict. Includes a stdlib Python checker with --self-test.
Answers enterprise security questionnaires for small teams: drafts each answer from your real policies and past replies, marks what needs proof or a fix, and keeps a reusable answer library.
Keeps a young company's legal and tax deadlines in one calendar: annual filings, tax returns, payroll and sales tax dates, licenses and trademark renewals, with reminders well before each one.
Tracks every cloud credit, SaaS startup discount and accelerator perk you have or could claim, warns before credits expire or plans flip to full price, and shows how much runway they add.
Gets a startup ready for investor due diligence: builds a clean data room checklist, finds missing or outdated documents, and answers investor requests from one place.