System BuildIntermediateGeneralEngineeringManufacturing

System Security & Launch Review Prompt

Produces a pre-launch security and reliability checklist for a new system.

Audience: IT, security, DevOps · Last updated 2026-07-17
Contents

Scenario

Produces a pre-launch security and reliability checklist for a new system.

Applicable Industry or Company Size

  • General
  • Engineering
  • Manufacturing

Preparation Before Use

  • A system architecture diagram.
  • A data flow diagram.

Variable Reference

VariableDescription
[Company Name]Your company's official name
[System Name]The name of the system
[Data Sensitivity]e.g., contains personal data, contains financial data, internal only

Full Prompt

Prompt
You are a security and reliability engineering consultant. Produce a launch checklist for the following system.

[Background]
- Company: [Company Name]
- System: [System Name]
- Data Sensitivity: [Data Sensitivity]

[Checklist Dimensions]
1. Identity and access (MFA, SSO, role permissions, offboarding process).
2. Data protection (encryption in transit, encryption at rest, backups, anonymization).
3. Application security (OWASP Top 10, dependency scanning, secrets management).
4. Monitoring and auditing (logging, alerting, retention).
5. High availability (RTO / RPO, fault tolerance, redundancy).
6. Supply chain and third parties (SaaS licensing, data processing agreements).
7. Incident response process.
8. Training and phishing drills.

[Output Format] A table: Dimension / Check Item / Judgment Criteria / Owner / Status. Do not recommend unverified specific security products.

[Handling uncertain information]
If any of the variables below have not been filled in or the information is insufficient, list the missing fields directly and ask the user — do not assume or fabricate data.

[Prohibited]
- Do not fabricate statistics, regulation numbers, certification names, or client case studies.
- When professional judgment is insufficient, explicitly mark "requires human confirmation" rather than inferring on your own.

[Final self-check]
After producing the output, list a self-check at the end covering: (1) whether any fabricated numbers, regulations, standards, or client names were used; (2) whether any unfilled but important variable was ignored; (3) whether assumptions are clearly labeled.

Usage Steps

  1. Fill in the variables.
  2. Review with security / compliance teams.
  3. Include in the go/no-go launch decision.

Example

A system handling personal data must complete data processing records and consent forms.

Common Mistakes

  • Only running functional tests while neglecting security testing.

Cautions

  • Personal-data and cross-border data handling must comply with local regulations.
Last updated 2026-07-17

Need further customization to fit your company's process and industry?

AEGIS POWER INTEGRATIONS offers AI adoption, process assessment, and systems integration consulting to help you turn prompts into a stable, working internal process.