> For the complete documentation index, see [llms.txt](https://docs.kangal.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kangal.dev/integrations/security.md).

# Credential and network security

Treat every integration as an outbound trust boundary.

## Credential handling

* Create a dedicated provider identity for Kangal.
* Grant only the scopes required by the selected driver.
* Prefer read-only access for inventory and observability sync.
* Enter credentials only in fields marked as secrets.
* Never place secrets in labels, organization names, URLs, or free-form notes.
* Rotate credentials according to the provider and company security policy.

Kangal does not return a saved secret in plaintext. When editing an existing integration, an empty secret field preserves the current stored value. Enter a new value only when rotating the credential.

## Outbound network policy

Custom provider endpoints must use public HTTPS unless the deployment has an explicitly approved private egress design. Enforce an egress allowlist, approve trusted HTTPS origins for every provider, and reject redirects to unapproved destinations.

Allow only the provider hosts and ports required by the integration. Verify:

* DNS resolution;
* trusted TLS certificate chains;
* proxy or firewall rules;
* Kubernetes NetworkPolicy or egress gateway rules;
* provider IP allowlists when applicable.

## Operational verification

After installation:

1. Run a manual sync.
2. Confirm the expected provider account, organization, group, or site.
3. Check that imported inventory matches the credential's intended scope.
4. Review the audit and sync-history records.
5. Confirm that API responses and logs contain no plaintext credentials.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kangal.dev/integrations/security.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.