Skip to main content
Once you’ve created a use case, Keldyn drafts its architecture and opens the Architecture Workspace — your home base for reviewing the system, running security analysis, and tracking progress against your frameworks. The overall journey follows three stages: Requirements → Design → Review.

Generate the architecture

After you submit a use case, Keldyn builds an architecture model from your requirements and answers. You’ll see a Generating Architecture screen while it works, then an Architecture Preview.
1

Review the preview

On the Architecture Preview, check the generated snapshot of your system.
2

Refine or continue

Select Review and Edit to open the architecture editor and adjust the model, or Continue to move into the workspace. Keldyn kicks off a security analysis in the background.

The Architecture Workspace

The workspace is organized into five tabs. You can change the use case’s lifecycle status (Draft, Under Review, Approved, Active, Production, Suspended, Retired) or edit it from the header.
TabWhat it’s for
Progress TrackerAn at-a-glance view of security coverage, compliance coverage, overall requirements complete, and architecture threat mitigation.
ComplianceTrack regulatory control requirements (for example GDPR and the EU AI Act) and their implementation.
SecurityTrack security controls and review the risks/CWEs surfaced by architecture analysis.
ArchitectureReview the generated model — summary, data flow and data asset diagrams, saved versions, and asset inventory.
Reporting HubAccess documents, exports, and your reporting posture.

Run security analysis

Keldyn analyzes your architecture for threats and weaknesses. Analysis runs automatically after generation, and you can re-run it whenever the design changes.
  • When something needs attention, an alert banner appears at the top of the workspace with actions like Run Analysis, Re-run Analysis, Review Risks, or Review Controls.
  • Results populate the Architecture Threats card on the Progress Tracker and the risk table on the Security tab.
Re-run the analysis after editing your architecture so threat and control data stays current.

Track requirements and risks

On the Compliance and Security tabs, each control appears as a row you can expand to see its description, implementation guidance, underlying threat, finding, and evidence. From there you can set a control’s status, assign an owner, or mark it not applicable. For details on working with controls, see Frameworks & controls. On the Security tab, the Architecture CWEs section lists risks from the analysis with their severity and a tracking state (for example Not Reviewed, In Progress, Mitigated, or Accepted) that you can update as you address them.

Next steps

Frameworks & controls

Enable frameworks and track control implementation across your organization and use cases.

Evidence & audits

Attach evidence to controls and manage audits and certifications.