# OT security posture

IntelFactor assumes an OT environment.

It is designed around segmentation, least privilege, and auditability.

### Network boundaries

* Production Zone stays isolated.
* Site Data Zone is the only approved aggregation point.
* Remote access is optional and separable.

### Default communication stance

* No outbound internet required for inspection.
* No inbound connectivity into OT by default.
* Only explicitly approved conduits are allowed.

### Identity and access

* Role-based access (operator vs QA vs admin).
* MFA for any remote access.
* Service-to-service auth uses short-lived credentials when possible.

### Audit expectations

* Evidence artifacts are traceable to outcomes.
* Admin actions are logged.
* Updates are signed and verifiable.

{% hint style="info" %}
If your security team maps to IEC 62443, IntelFactor fits typical zone/conduit reviews. The exact hardening checklist is site-specific.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://intelfactor.gitbook.io/doc/home/security/ot-security-posture.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.