# Security

> Secure applications built with TX Text Control .NET Server: authentication, access tokens, WebSocket checks, document protection, signing, deployment and SBOMs.

- **Product:** TX Text Control .NET Server
- **Section:** Documentation
- **Kind:** Topic
- **Path:** TX Text Control .NET Server > Security
- **Web URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/security/
- **LLMs URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/security/llms.txt
- **LLMs-Full URL:** https://docs.textcontrol.com/tx-text-control-dotnet-server/security/llms-full.txt

---

## On This Page

- [Where Security Applies](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/#where-security-applies)
- [Find the Right Page](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/#find-the-right-page)
- [Where to Start](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/#where-to-start)

---

## In This Section

- [Access Tokens](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/access-tokens/llms.txt): Protect the Document Editor and Viewer with access tokens: issue per-user tokens, pass them from each frontend, check viewer requests, lifetimes and logs.
- [Authentication](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/authentication/llms.txt): Protect TX Text Control endpoints with ASP.NET Core: middleware order, a fallback policy, policies for actions, per-document checks and the signing endpoint.
- [Compliance](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/compliance/llms.txt): Map compliance requirements to TX Text Control: PDF/A archiving, PDF/UA accessibility, e-invoices, eIDAS signature levels, GDPR, the CRA and ISO 27001.
- [Secure Deployment](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/deployment/llms.txt): Harden a TX Text Control deployment: HTTPS and wss, a private Document Editor backend port, least-privilege accounts, no secrets in images, logs and updates.
- [Document Security](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/documents/llms.txt): Protect document content with TX Text Control: PDF encryption and permissions, encrypted input, editor protection, redaction, hidden data and watermarks.
- [Security Overview](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/overview/llms.txt): Review where TX Text Control processes documents, which endpoints and TCP port 4283 an application exposes and which protections your own code has to add.
- [SBOM](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/sbom/llms.txt): Signed CycloneDX SBOMs for TX Text Control NuGet packages: what they list, which packages they cover, how to request them and how to audit your dependencies.
- [Digital Signatures](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/signatures/llms.txt): Secure a signing process: what signatures protect, private keys, a protected signing endpoint, timestamps, checking received PDF files and audit trails.
- [WebSocket Security](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/websockets/llms.txt): Secure the Document Editor's WebSocket: wss, a token check in the handshake, allowed origins, endpoints that take connection IDs and the private backend link.

---

## Nearby

- **Previous:** [CI/CD](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/ci-cd/llms.txt)
- **Next:** [Security Overview](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/overview/llms.txt)