# Security > How WPF applications with TX Text Control protect documents: editable regions, received files, encrypted PDF output, signing certificates and release checks. - **Product:** TX Text Control .NET for WPF - **Section:** Documentation - **Kind:** Topic - **Path:** TX Text Control .NET for WPF > Security - **826 words** - **Web URL:** https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/ - **LLMs URL:** https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/llms.txt - **LLMs-Full URL:** https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/llms-full.txt --- A WPF application with TX Text Control keeps its documents on the desktop: the editor, the engine and the files all live on the user's computer. Security therefore rests on two things, the protection built into the documents and the decisions your application makes about users, passwords, certificates and the files it installs. Whether you design such an application or review one, what follows explains what TX Text Control protects, where that protection ends and what your code adds. ### Four Places to Look - **The editor.** Protected documents and editable regions limit what users change in the `TextControl`, based on user names that your application provides. - **Incoming documents.** Files from others can fail to load, be encrypted or contain links and file paths. Your code decides what is imported and what a click on a link does. - **Outgoing documents.** Passwords encrypt PDF documents, permissions ask PDF readers to restrict actions and digital signatures reveal changes. - **The release.** Licensing files and feed credentials stay out of the installer, and the components you ship stay current. ### Find the Right Page | If you want to | Read | |---|---| | See the security model of a desktop application with TX Text Control | [Security Overview](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/overview/llms-full.txt) | | Learn what document protection prevents and how to set user names from your sign-in | [Document Protection and User Permissions](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/document-protection/llms-full.txt) | | Open files from other people with limited formats, safe links and error handling | [Handling Untrusted Documents](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/untrusted-documents/llms-full.txt) | | Delete sensitive text for good before a document is passed on | [Redact Text](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/untrusted-documents/#redact-text) | | Protect PDF documents, apply the permissions of opened PDF files and verify encryption | [PDF Passwords and Permissions](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/pdf-passwords/llms-full.txt) | | Plan where signing keys are kept and who can sign with them | [Certificate and Private Key Handling](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/certificates/llms-full.txt) | | Go through the checks before a release, from licensing files to SBOMs | [Secure Application Deployment](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/deployment/llms-full.txt) | ### Where to Start 1. Read [Security Overview](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/overview/llms-full.txt) for the model and a comparison of the mechanisms. 2. Continue with the page that matches your application: protecting documents in the editor, opening documents from outside or creating protected PDF files. 3. Work through [Secure Application Deployment](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/deployment/llms-full.txt) before you ship. How each mechanism is used in code is shown in the feature sections: [Document Protection and Editable Regions](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/document-editor/protection/llms-full.txt), [Passwords and Access Permissions](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/pdf/passwords/llms-full.txt) and [Digital Signatures](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/digital-signatures/llms-full.txt). ### Pages in This Section - [Security Overview](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/overview/llms-full.txt) — where documents are processed, what TX Text Control protects and what your application decides. - [Document Protection and User Permissions](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/document-protection/llms-full.txt) — the limits of protected documents and safe user names. - [Handling Untrusted Documents](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/untrusted-documents/llms-full.txt) — the Open dialog box, load errors, links, file references and text redaction. - [PDF Passwords and Permissions](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/pdf-passwords/llms-full.txt) — encryption, permissions and a check of the output. - [Certificate and Private Key Handling](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/certificates/llms-full.txt) — the places a signing key can live and what each means. - [Secure Application Deployment](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/deployment/llms-full.txt) — the checklist for a release. --- ## In This Section - [Certificate and Private Key Handling](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/certificates/llms-full.txt): Plan signing in a WPF application: X509Certificate2 keys in PFX files, the current user's certificate store or on smart cards, test certificates and timestamps. - [Secure Application Deployment](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/deployment/llms-full.txt): Check a WPF release with TX Text Control: licensing files and feed credentials out of the installer, AppContainer packaging, current service packs and SBOMs. - [Document Protection and User Permissions](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/document-protection/llms-full.txt): Know what protected documents in the WPF TextControl prevent and allow, assign UserNames from your sign-in and unlock files in code with MasterPassword. - [Security Overview](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/overview/llms-full.txt): The security model of a WPF desktop app with TX Text Control: in-process engine, document protection, PDF encryption, signatures and your app's own duties. - [PDF Passwords and Permissions](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/pdf-passwords/llms-full.txt): UserPassword, MasterPassword and PDF permissions compared: apply the permissions of an opened PDF to the WPF TextControl and check saved files for encryption. - [Handling Untrusted Documents](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/untrusted-documents/llms-full.txt): Load received files in the WPF TextControl safely: restrict file filters, skip images and links, handle FilterException, check link targets and redact text. --- ## Nearby - **Previous:** [CI/CD](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/deployment/ci-cd/llms-full.txt) - **Next:** [Security Overview](https://docs.textcontrol.com/tx-text-control-dotnet-wpf/security/overview/llms-full.txt)