CIVITAS

Request intake

For Security Review Jumpstart and scoped evidence-pack inquiries. The goal is to get enough context for a useful scoped reply, not to route you into a placeholder.

Email stays the default channel because scope, artifacts, and constraints are easier to review, forward, and verify in a written thread. No public upload form. No routine calls.

What to send

  • selected service: Security Review, AI Governance, EU AI Act, or NIS2
  • company type, employee band, and the responsible owner
  • product/system scope and what is in/out
  • current pressure: customer review, questionnaire, regulatory, or procurement
  • deadline, reviewer window, or internal timing constraint
  • evidence transfer method and sensitive-data flag
  • external LLM processing permission; default is no

Why email

  • it supports direct artifact and file links without reformatting
  • it keeps scope, questions, and decisions in an attributable written thread
  • it fits the async operating model; there is no form and no routine call scheduling

What happens next

  1. Acknowledgement typically lands inside 1 business day. If key context is missing, the first reply asks for it.
  2. Scope triage usually follows in 2-3 business days, depending on materials and constraints.
  3. If there is fit, you receive a bounded email outline covering deliverables, boundaries, next step, and expected working cadence.