Adaptive Cards are a JSON-based card format for building rich, interactive UI content that can be rendered in chat apps, productivity tools and other hosts. The card structure defines text, images, inputs and actions, while the host application renders the layout within its own interface and capabilities.
What Adaptive Cards Are Used For
Adaptive Cards are a portable way to package interactive content, so the same JSON definition can appear inside different hosts without the author hard-coding layout for each one. That makes them useful when a product needs structured content, form-like inputs or action buttons that still feel native to the host experience.
Because the host renders the card, the card author defines the content and intent, while the host decides how much of that structure it supports. In practice, that separation gives teams a single content format, but it also means visual fidelity and interaction behaviour can vary across platforms.
How the Card Schema Works
The schema is the core of Adaptive Cards. It describes the building blocks, such as text, images, inputs and actions, and arranges them into a JSON object that a renderer can interpret. This makes the format machine-readable, portable and easier to generate dynamically than a hand-built screen design.
Each card is intentionally declarative rather than procedural. The card says what should appear and what the user can do, but it does not control the host application’s broader UI logic. That design keeps the format flexible, while also constraining it to the components and rules supported by the renderer.
Where Adaptive Cards Fit in Application Design
Adaptive Cards are strongest when the same message, task or workflow needs to travel across multiple environments, such as chat systems, collaboration tools or productivity platforms. They reduce the need to build separate native interfaces for each host, which helps standardise user interactions across channels.
They are less useful when a team needs highly bespoke interaction patterns or precise control over every visual detail. The host may limit available features, so the card author should treat the format as a shared contract between content creator and rendering platform, not as a full replacement for a custom front end.
Security and Trust Implications
Because Adaptive Cards can carry actionable content, they need the same scrutiny as other user-facing application surfaces. A card may include links, buttons, form fields or data that influence user decisions, so the surrounding application must treat the rendered output as untrusted content until it has been validated and authorised.
When cards are used in enterprise workflows, the main security question is not the JSON syntax itself but what the host permits the card to request, display or trigger. If the host accepts card content from a weaker trust boundary, the card becomes a delivery path for misleading UI, unsafe navigation or overbroad interaction in the host context.
Risk and Threat Considerations
Adaptive Cards create risk when a trusted host renders content from an untrusted source, because the card can shape user behaviour inside an interface that looks familiar and legitimate. The main concern is not code execution in the card format itself, but deception, unsafe actions and the misuse of trust between the card author, host and end user.
Failure mechanism: A hostile or compromised content source can supply a card that encourages a user to click, submit or approve something they would not accept outside the host application, especially when the UI appears native to the platform.
Impact: That trust abuse can lead to credential theft, fraudulent approvals, data exposure or workflow manipulation, depending on what the host allows the card to do.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, OWASP ASVS and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-3 — Access Enforcement | Adaptive Cards can trigger host actions that need enforced permissions. |
| IA-2 — Identification and Authentication (Organizational Users) | Cards may expose approval or sign-in flows that depend on user authentication. | |
| SI-10 — Information Input Validation | Card payloads are structured input that the host must validate before rendering or acting. | |
| Recommendation — Enforce AC-3 on every card-triggered action before the host accepts or executes it. Require IA-2 before allowing cards to initiate sensitive user workflows. Apply SI-10 to validate card content, fields and actions before rendering. | ||
| OWASP ASVS | V8 — Authorization | Interactive cards often expose actions that must be authorised in the application layer. |
| Recommendation — Verify V8 controls on every action exposed through the card UI. | ||
| NIST CSF 2.0 | PR.AA-05 — Identity Management, Authentication and Access Control | Card-driven workflows still depend on access control around the host application. |
| Recommendation — Map card actions to PR.AA-05 and restrict them to authorised users only. | ||
Practitioner Guidance
Why practitioners should care: Treat Adaptive Cards as an application trust boundary, not just a presentation format. The card definition may be portable, but the real control point is the host’s policy for who can publish cards, which actions are allowed and what data the renderer may consume.
What to watch for: Review card content from the perspective of user intent and downstream action. If a card asks for input, redirects the user or wraps an approval flow, the host should enforce the same validation, authorization and provenance checks you would expect for any other interactive business process.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 3, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org