# 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 - **794 words** - **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 --- An application built with TX Text Control .NET Server is secured in three places: at the endpoints that the Document Editor and the Document Viewer add to it, in the documents it creates and on the servers it runs on. TX Text Control runs entirely in your environment and leaves the decision about who may do what to your application. For developers who take such an application to production, and for the teams who review it, the pages of Security explain what TX Text Control provides in each place and what the application adds. ### Where Security Applies - **The endpoints.** The Document Editor connects over a WebSocket at `/api/TXWebSocket`, the Document Viewer calls a controller named `TextControl`, and your own controllers load, save and sign documents. ASP.NET Core authentication, access tokens and a check of the WebSocket handshake decide who may use them. - **The documents.** PDF documents can be encrypted and restricted with permissions, documents can be protected while they're edited, confidential text can be redacted and hidden data removed, and digital signatures make changes detectable. - **The deployment.** HTTPS, a Document Editor backend that only your application reaches, accounts with few rights and secrets that stay out of the output protect the servers. Signed SBOMs of the TX Text Control packages and the compliance topics complete the picture. ### Find the Right Page | If you want to | Read | |---|---| | Understand where documents are processed and which endpoints and ports an application exposes | [Security Overview](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/overview/llms-full.txt) | | Require signed-in users, apply policies and check access to each document | [Authentication](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/authentication/llms-full.txt) | | Protect the editor and the viewer with tokens, for example for Angular or React frontends | [Access Tokens](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/access-tokens/llms-full.txt) | | Check the WebSocket handshake of the Document Editor and restrict its origins | [WebSocket Security](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/websockets/llms-full.txt) | | Encrypt PDF documents, protect documents in the editor, redact text and remove hidden data | [Document Security](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/documents/llms-full.txt) | | Keep signing certificates safe and accept signed documents only from your own signing processes | [Digital Signatures](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/signatures/llms-full.txt) | | Get the SBOMs of the TX Text Control packages and check your dependencies for vulnerabilities | [SBOM](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/sbom/llms-full.txt) | | Harden a production deployment: HTTPS, the backend port, accounts, secrets and updates | [Secure Deployment](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/deployment/llms-full.txt) | | Answer questions about archiving, accessibility, signatures, data protection and the Cyber Resilience Act | [Compliance](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/compliance/llms-full.txt) | ### Where to Start 1. [Security Overview](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/overview/llms-full.txt): the parts of an application and what each of them needs. 2. [Authentication](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/authentication/llms-full.txt): protect the endpoints of the editor, the viewer and your controllers. 3. [WebSocket Security](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/websockets/llms-full.txt) when your application uses the Document Editor, and [Access Tokens](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/access-tokens/llms-full.txt) when its frontend runs on another origin. 4. [Secure Deployment](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/deployment/llms-full.txt) before the application goes into production. The [Deployment Guide](https://docs.textcontrol.com/tx-text-control-dotnet-server/deployment/llms-full.txt) shows the complete setup of each platform, and [Digital Signatures](https://docs.textcontrol.com/tx-text-control-dotnet-server/digital-signatures/llms-full.txt) covers signing documents from the first certificate to validation. --- ## In This Section - [Access Tokens](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/access-tokens/llms-full.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-full.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-full.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-full.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-full.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-full.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-full.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-full.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-full.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-full.txt) - **Next:** [Security Overview](https://docs.textcontrol.com/tx-text-control-dotnet-server/security/overview/llms-full.txt)