---
title: Other files that can be encrypted
description: Encrypt additional PingDirectory files, including key store PINs, tool password files, properties files, and LDIF read and written by tools.
component: pingdirectory
version: 10.2
page_id: pingdirectory:pingdirectory_security_guide:pd_sec_other_files_encrypted
canonical_url: https://docs.pingidentity.com/pingdirectory/11.1/pingdirectory_security_guide/pd_sec_other_files_encrypted.html
llms_txt: https://docs.pingidentity.com/pingdirectory/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2023-09-13T00:00:00Z
superseded_by: https://docs.pingidentity.com/pingdirectory/11.1/pingdirectory_security_guide/pd_sec_other_files_encrypted.html
---

# Other files that can be encrypted

The PingDirectory server and accompanying tools support interacting with a variety of other types of encrypted files.

Examples of this include:

* The files containing the PIN needed to access a certificate key or trust store, such as the `ads-truststore.pin`, `keystore.pin`, and `truststore.pin` files in the server's config directory, can be encrypted.

* If a command-line tool needs to read a password from a file, such as when using the `--bindPasswordFile`, `--keyStorePasswordFile`, or `--trustStorePasswordFile` arguments offered by LDAP-enabled tools, it should be able to read from encrypted files.

* If a command-line tool supports obtaining default argument values from a properties file, such as from `config/tools.properties`, that properties file can be encrypted.

* When writing its output to one or more files, the `ldapsearch` tool can encrypt the data as it is written.

* When reading the set of changes to process, the `ldapmodify` and `parallel-update` tools can read those changes from encrypted LDIF files.

* LDIF tools like `ldifsearch`, `ldifmodify`, and `ldif-diff` support reading from and writing to encrypted LDIF files.