--- name: navan-security-basics-cccd0d670595 description: >- Threat-model a Navan integration across identity, travel, expense, payment, file, and downstream systems. Use when performing design or security review. Trigger with "secure Navan integration", "Navan threat model", or "review Navan data flow". allowed-tools: Read,Glob,Grep,Write,Edit argument-hint: " " version: 1.9.0 license: MIT author: Jeremy Longshore tags: [saas, navan, security] model: inherit effort: high compatibility: "Designed for Claude Code; live or external Navan actions require network access and explicit approval" --- # Navan Integration Security Boundary ## Overview Threat-model a Navan integration across identity, travel, expense, payment, file, and downstream systems. This workflow produces an auditable decision or artifact before any live action. ## Prerequisites - Access to the selected tenant's current Navan Help Center and contracted integration documentation. - A named business owner and data owner for the travel or expense workflow. - A non-production evidence set with secrets and traveler data removed. ## Current Contract Navan states that its APIs undergo security testing and that data in transit and sensitive data at rest are encrypted. Those vendor controls do not replace customer-side least privilege, downstream encryption, retention, monitoring, or third-party AI governance. ## Authentication Use dedicated integration identities, scoped access, approved secret storage, host binding, rotation, and revocation. Keep interactive admin and automation credentials separate. ## Instructions 1. Draw trust boundaries from Navan through every processor and destination. 2. Classify credentials and traveler, itinerary, payment, receipt, profile, and location data. 3. Minimize fields, purposes, destinations, retention, and human access. 4. Model credential theft, tenant mix-up, injection, replay, exfiltration, and confused-deputy paths. 5. Add deny-by-default network, logging, artifact, and AI-tool policies. 6. Test detection, containment, revocation, reconciliation, and notification paths. ## Tool Discipline Use Read, Glob, and Grep to inspect documentation, schemas, configuration, code, fixtures, and evidence. Use Write and Edit only for approved repository artifacts. Invocation alone does not authorize network access, credentials, traveler or expense data, bookings, payments, policy or identity changes, file transfers, deployments, or deletion. ## Approval Boundaries Any new processor, third-party AI or MCP connection, broader scope, production secret, cross-border transfer, or sensitive-data export requires security and data-owner approval. ## Error Handling - Do not put traveler or receipt content in prompts or logs by default. - Certification badges are not authorization for a new use. - Fail closed on tenant, host, identity, or destination ambiguity. ## Output Return a data-flow diagram, threat register, control owners, residual risks, approval boundaries, and verification plan. Identify assumptions, owners, expirations, and evidence gaps explicitly. ## Examples - Review a Booking API feed into a duty-of-care vendor. - Constrain an MCP assistant to a minimal approved itinerary view. ## Validation Exercise tenant isolation, revoked credentials, malicious fields, log redaction, unauthorized destination, and incident containment. Record expected and observed results, including fail-closed behavior. ## Resources - [Current first-party evidence map](references/official-docs.md) — recheck dated sources and the selected tenant's in-account contract before relying on mutable endpoints, fields, entitlements, limits, or delivery behavior. - Record tenant observations as environment-specific evidence, never universal Navan guarantees. --- Source attribution: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/navan-pack/skills/navan-security-basics/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice MIT License Copyright (c) 2025 Jeremy Longshore Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Mega AI Hub resource metadata Creator / publisher: jeremylongshore Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/navan-pack/skills/navan-security-basics/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Backend Developer, DevOps / SRE, Security Engineer Specialties: API, Backend, Design, Word Documents, Frontend, Git, Testing Tools: AWS, Navan Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: b031ed7d433dc15403cf7c64036698da5c959e100eec2fa42a526e7be9263dd4