AgentenCode evidence profileCoding

✓ Editorially reviewedChecked: September 30, 2026

Agent profile · Coding

Kiro

Kiro is classified by AgentenCode as an agentic development environment from AWS. It belongs to the Coding category. This English profile does not maintain a separate factual record: it renders the same underlying evidence, trust and history data as the German profile.

AWSCodingDevelopers & teams

View profile ↓Check sources ↓

Codingeditorial classification

AWSprovider

8 primary sourcessource status

September 30, 2026last verification

AgentenTrust 2.0 · EU & governance evidence

Trust, privacy and control evidence for Kiro

Direct answer: AgentenCode currently documents 5 of 36 normalized trust controls for this profile. Missing fields remain Unknown and are never automatically interpreted as “no”.

EU AI ActEvidence context only. AgentenCode does not infer legal applicability or compliance from individual product controls.

GDPRPrivacy and security signals are documented field by field. Data residency alone is not a compliance or transfer assessment.

Privacy contextPrivacy & data0 of 8 documentedResidency, training, retention, DPA, subprocessors and processing scope.

Security contextSecurity & access3 of 10 documentedEncryption, SSO, SCIM, RBAC, roles and credential handling.

Human controlHuman control0 of 10 documentedApproval, oversight, permissions and stop or rollback controls.

TraceabilityAudit & traceability2 of 8 documentedAudit logs, APIs, SIEM, observability, tracing and activity history.

Important: these numbers show evidence coverage, not a product rating. 0 of 10 means that no field-level public evidence is stored for those ten controls in the current dataset. It does not mean the product lacks those capabilities.

Field-level evidence

Documented controls and values from primary sources.

Documented yesDocumented valueUnknown remains unknown

High confidence

API · Rest

Yes — documented

Kiro Crew exposes documented REST endpoints.

Scope: kiro_crew_gateway · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · Available

Yes — documented

Kiro Enterprise provides activity and prompt logging for audit/monitoring.

Scope: kiro_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Governance · Audit logs · SIEM export

Yes — documented

Kiro enterprise prompt logs can be exported to customer-controlled S3 for downstream SIEM/analytics workflows.

Scope: kiro_enterprise_prompt_logs · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Managed

Yes — documented

Kiro supports a managed cloud-sandbox runtime.

Scope: kiro_cloud_sessions · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Private Network

Yes — documented

Kiro supports private VPC connectivity via AWS PrivateLink.

Scope: kiro_api_private_connectivity · verified 2026-10-01 · Primary source ↗

High confidence

Hosting · Self Hosted

Yes — documented

Kiro IDE/CLI can run in the user's local/customer-managed environment.

Scope: kiro_ide_cli_local_runtime · verified 2026-10-01 · Primary source ↗

High confidence

Protocols · Mcp · Client

Yes — documented

Kiro acts as an MCP client.

Scope: kiro_ide_cli_web · verified 2026-10-01 · Primary source ↗

High confidence

Security · Customer-managed keys

Yes — documented

Kiro Enterprise supports customer-managed KMS keys.

Scope: kiro_enterprise · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · At rest

Yes — documented

Kiro encrypts service data at rest.

Scope: kiro_data · verified 2026-10-01 · Primary source ↗

High confidence

Security · Encryption · In transit

TLS 1.2+

Kiro documents TLS 1.2+ encryption in transit.

Scope: kiro_data · verified 2026-10-01 · Primary source ↗

Evidence-backed overview

What is Kiro?

Product-specific evidence for Kiro

This profile links 8 unique primary sources across the product profile, field-level evidence, trust controls and documented relations. The points below describe this product’s stored evidence rather than generic characteristics of Coding.

Customer-Managed Keys

Yes · Scope: kiro_enterprise · verified 2026-10-01.

Primary source ↗

Verschlüsselung at rest

Yes · Scope: kiro_data · verified 2026-10-01.

Primary source ↗

Verschlüsselung in transit

TLS 1.2+ · Scope: kiro_data · verified 2026-10-01.

Primary source ↗

Audit Logs

Yes · Scope: kiro_enterprise · verified 2026-10-01.

Primary source ↗

SIEM Export

Yes · Scope: kiro_enterprise_prompt_logs · verified 2026-10-01.

Primary source ↗

protocols · mcp · client

Yes · Scope: kiro_ide_cli_web · verified 2026-10-01.

Primary source ↗

AgentenCode treats this page as a reference profile rather than a ranking. Product facts are separated from editorial classification, and the profile is tied to a specific verification date. If a capability is not backed by sufficiently precise public evidence, it remains unknown instead of being inferred from marketing language or from similar products.

1primary source

10field-level evidence claims

5documented trust controls

2history events

How to read the evidence

The field-level evidence layer records a value, a scope, a confidence level, a verification date and one or more primary sources. Scope matters: an enterprise-only security feature must not be generalized to every plan or deployment surface. The same rule applies to hosting, privacy, audit and protocol claims.

AgentenCode also keeps Unknown distinct from false. A missing claim means the public dataset does not currently contain sufficiently precise evidence for that field. A negative value is used only when a reliable primary source explicitly documents a restriction or non-availability.

Decision context

Provider and category

Kiro is documented under Coding and is associated with AWS. Category labels help navigation but do not replace product-specific evidence.

Verification status

The public profile is marked editorially reviewed and was last checked on September 30, 2026.

Trust coverage

5 of 36 normalized trust controls currently have field-level public evidence. The remaining controls are not treated as negative findings.

Source-first use

For procurement, security or legal decisions, use the linked primary sources and verify the plan, region and configuration that apply to your organization.

Capabilities, strengths and deployment checks for Kiro

Kiro is classified as Agentische Entwicklungsumgebung from AWS. The profile’s editorial layer is derived from the stored use cases, strengths and checks below; claims about security, privacy or governance remain separate and require field-level evidence.

Spec-getriebene Entwicklung

This use case is part of the stored profile for Kiro. The related strength is “Specs als Arbeitsgrundlage”. In a production evaluation, the practical boundary to verify is: Autopilot- und Tool-Rechte bewusst konfigurieren.

Feature-Umsetzung

This use case is part of the stored profile for Kiro. The related strength is “IDE und CLI”. In a production evaluation, the practical boundary to verify is: Generierte Änderungen prüfen.

Automatisierung

This use case is part of the stored profile for Kiro. The related strength is “MCP und Tool-Erweiterung”. In a production evaluation, the practical boundary to verify is: Teamstandards in Specs und Reviews verankern.

Codebase-Arbeit

This use case is part of the stored profile for Kiro. The related strength is “Agentische Automatisierung”. In a production evaluation, the practical boundary to verify is: Autopilot- und Tool-Rechte bewusst konfigurieren.

What to verify before adoption

Autopilot- und Tool-Rechte bewusst konfigurieren. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Generierte Änderungen prüfen. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.
Teamstandards in Specs und Reviews verankern. Treat undocumented controls as Unknown and verify the exact plan, region and deployment scope.

Editorial boundary: The use-case and strength descriptions are product-specific editorial context based on the stored profile. Trust, privacy and governance statements are only presented as facts when field-level primary-source evidence exists.

Verified history

The public history layer records only confirmed profile changes and verification events. Monitoring signals are not published as product facts until they have been reviewed.

September 30, 2026 · Verification Update
September 28, 2026 · Schema Upgrade

Official sources

This profile links 8 unique primary sources across the product profile, field-level evidence, trust layer and documented relations. Provider documentation remains authoritative when the product changes between verification cycles.

Frequently asked questions

What is Kiro?

Kiro is listed by AgentenCode as a coding agent or agentic product from AWS.

How much trust evidence is documented for Kiro?

The current trust layer documents 5 of 36 normalized controls. Missing controls remain unknown rather than being treated as false.

When was this profile last checked?

The current profile verification date is September 30, 2026. The linked primary sources remain authoritative if the product changes between checks.

Method note: AgentenCode does not certify GDPR or EU AI Act compliance. It documents evidence that can support a separate legal, security or procurement assessment.