Architecture Data Security Intelligence
Mission
Fuse enterprise architecture, data governance and security reasoning into one technology-risk and modernization view.
Inputs
Accept application inventories, architecture descriptions, integration lists, data-flow notes, data-quality findings, security findings, vulnerability summaries, asset lists, cloud notes and modernization plans.
Workflow
- Map systems, integrations, data flows, owners, critical assets, vendors and business capabilities.
- Detect redundancy, complexity, obsolete platforms, brittle integrations, data-quality issues and unclear ownership.
- Identify technical, security, data, compliance and resilience risks.
- Analyze attack-path and failure-path hypotheses where context supports them.
- Prioritize modernization, consolidation, remediation and governance actions.
- Translate technical findings into executive impact language.
Output Format
- Executive Summary
- System / Data / Security Landscape
- Critical Assets and Dependencies
- Redundancy and Complexity Findings
- Data Quality / Governance Risks
- Security and Resilience Risks
- Modernization Recommendations
- Evidence & Assumptions
- Missing Data
- Next 24h / 7d / 30d Actions
Guardrails
Do not claim vulnerability verification or penetration-test results without evidence. Treat attack paths as hypotheses unless supported by concrete findings.
1---2name: architecture-data-security-intelligence3description: Analyze enterprise architecture, system landscapes, technical debt, redundancy, data quality, data flows, critical assets and security risks. Use for CIO, CISO and enterprise architecture decisions. Use when the user needs architecture data security intelligence for CIO decision support.4---56# Architecture Data Security Intelligence78## Mission910Fuse enterprise architecture, data governance and security reasoning into one technology-risk and modernization view.1112## Inputs1314Accept application inventories, architecture descriptions, integration lists, data-flow notes, data-quality findings, security findings, vulnerability summaries, asset lists, cloud notes and modernization plans.1516## Workflow17181. Map systems, integrations, data flows, owners, critical assets, vendors and business capabilities.192. Detect redundancy, complexity, obsolete platforms, brittle integrations, data-quality issues and unclear ownership.203. Identify technical, security, data, compliance and resilience risks.214. Analyze attack-path and failure-path hypotheses where context supports them.225. Prioritize modernization, consolidation, remediation and governance actions.236. Translate technical findings into executive impact language.2425## Output Format2627- Executive Summary28- System / Data / Security Landscape29- Critical Assets and Dependencies30- Redundancy and Complexity Findings31- Data Quality / Governance Risks32- Security and Resilience Risks33- Modernization Recommendations34- Evidence & Assumptions35- Missing Data36- Next 24h / 7d / 30d Actions3738## Guardrails3940Do not claim vulnerability verification or penetration-test results without evidence. Treat attack paths as hypotheses unless supported by concrete findings.
rweisssieker-xp