Answer: Kiro requires explicit approval before writing to protected paths; when the agent attempts to create or modify a file matching a protected pattern, you see a confirmation prompt and the change is not applied until you approve it. The supported match types are "Path contains" and "Exact basename". Status: Confirmed Entry: tool/kiro/permissions-and-security/protected-paths Revision: 2 Digest: sha256:6f64cee1166799ff (changes whenever the content changes) Timeline: Created: 2026-11-13T03:44:13Z Last changed: 2026-11-20T13:31:31Z (Approval behavior: — → you see a confirmation prompt and the change is not applied until you approve it) Last verified: 2026-11-20T13:31:31Z Next check: 2026-11-21T13:31:31Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Match type 1 | Path contains | [1] | 2026-11-20 Match type 2 | Exact basename | [1] | 2026-11-20 Protected pattern example | .vscode/ | [1] | 2026-11-20 Approval behavior | you see a confirmation prompt and the change is not applied until you approve it | [1] | 2026-11-20 Sources: [1] Amazon Web Services. "Privacy and Security - Docs - Kiro". https://kiro.dev/docs/privacy-and-security/ Role: primary. Accessed: 2026-11-20T13:31:31Z Quote: "Path contains — Matches if the pattern appears anywhere in the file path." (Supports: Match type 1) Quote: "Exact basename — Matches if the filename (the last segment of the path) exactly equals the pattern." (Supports: Match type 2) Quote: ".vscode/ Path contains VS Code workspace settings" (Supports: Protected pattern example) Quote: "you see a confirmation prompt and the change is not applied until you approve it" (Supports: Approval behavior) Published: 2026-11-20T07:39:25Z Snapshot SHA-256: 2a27777037863f292c7fdc481c16399c726b0099bc5e7d7c1945f8ad94e5abf8 (captured 2026-11-20T13:31:31Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T13:31:31Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:31:31Z Last attempt: 2026-11-20T13:31:31Z Notes and limitations: Extracted automatically from a single official source (section "Protected paths"). Related: https://latestn.com/tool/kiro/permissions-and-security/remote-extensions-security What security risks do remote extensions pose in Kiro and how should I handle them? https://latestn.com/tool/kiro/permissions-and-security/required-iam-permissions-general What IAM permissions does Kiro require for general use? https://latestn.com/tool/kiro/permissions-and-security/review-converted-permissions How do I review converted permissions after upgrading Kiro CLI to V3? https://latestn.com/tool/kiro/permissions-and-security/power-oauth-authorization Which Powers require OAuth authorization in Kiro, and how do I authorize or disconnect one? https://latestn.com/tool/kiro/permissions-and-security/protect-mcp-api-keys-tokens How do I protect API keys and tokens when configuring MCP servers in Kiro? https://latestn.com/tool/kiro/permissions-and-security/protect-secrets-kiroignore How do I use .kiroignore to protect API keys and secrets from Kiro? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:31:31Z | changed | Approval behavior: — → you see a confirmation prompt and the change is not applied until you approve it | [1] 2026-11-20T13:31:31Z | changed | Protected pattern example: — → .vscode/ | [1] 2026-11-20T13:31:31Z | changed | Enforcement: Protected paths are enforced in the Kiro IDE. → — | [1] 2026-11-20T13:31:31Z | changed | Behavior: Kiro pauses and displays a confirmation prompt → — | [1] 2026-11-13T03:44:13Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/kiro/permissions-and-security/protected-paths/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/kiro/permissions-and-security/protected-paths POST: https://latestn.com/dispute/tool/kiro/permissions-and-security/protected-paths with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/kiro/permissions-and-security/protected-paths?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I set up protected paths in Kiro and what match types are supported? Revision 2, last verified 2026-11-20T13:31:31Z. https://latestn.com/tool/kiro/permissions-and-security/protected-paths (accessed 2026-11-21T10:01:23Z). @misc{LatestN_tool_kiro_permissions_and_security_protected_paths_r2, title = {How do I set up protected paths in Kiro and what match types are supported?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/kiro/permissions-and-security/protected-paths}}, note = {Revision 2; digest sha256:6f64cee1166799ff; last verified 2026-11-20T13:31:31Z; accessed 2026-11-21T10:01:23Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/kiro/permissions-and-security/protected-paths