mirror of
https://github.com/privacyguides/i18n.git
synced 2025-06-25 20:22:39 +00:00
359 lines
24 KiB
Markdown
359 lines
24 KiB
Markdown
---
|
||
meta_title: "推奨される暗号化ソフトウェア：VeraCrypt、Cryptomator、PicoCrypt、OpenPGP - Privacy Guides"
|
||
title: "暗号化ソフトウェア"
|
||
icon: material/file-lock
|
||
description: データの暗号化は、誰がデータにアクセスできるかをコントロールする唯一の方法です。 これらのツールを使えば、電子メールやその他のファイルを暗号化できます。
|
||
cover: encryption.webp
|
||
---
|
||
|
||
データの暗号化は、誰がデータにアクセスできるかをコントロールする唯一の方法です。 現在、ハードディスクや電子メール、ファイルの暗号化ソフトウェアを使用していない場合は、以下のツールを使いましょう。
|
||
|
||
## 複数プラットフォーム
|
||
|
||
ここに記載されているオプションは複数のプラットフォームに対応しており、データの暗号化バックアップの作成に適しています。
|
||
|
||
### Cryptomator（クラウド）
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
|
||
**Cryptomator** is an encryption solution designed for privately saving files to any cloud provider. It allows you to create vaults that are stored on a virtual drive, the contents of which are encrypted and synced with your cloud storage provider.
|
||
|
||
[:octicons-home-16: Homepage](https://cryptomator.org){ .md-button .md-button--primary }
|
||
[:octicons-eye-16:](https://cryptomator.org/privacy){ .card-link title="Privacy Policy" }
|
||
[:octicons-info-16:](https://docs.cryptomator.org/){ .card-link title=Documentation}
|
||
[:octicons-code-16:](https://github.com/cryptomator){ .card-link title="Source Code" }
|
||
[:octicons-heart-16:](https://cryptomator.org/donate/){ .card-link title=Contribute }
|
||
|
||
??? downloads
|
||
|
||
- [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=org.cryptomator)
|
||
- [:simple-appstore: App Store](https://apps.apple.com/us/app/cryptomator-2/id1560822163)
|
||
- [:simple-android: Android](https://cryptomator.org/android)
|
||
- [:simple-windows11: Windows](https://cryptomator.org/downloads)
|
||
- [:simple-apple: macOS](https://cryptomator.org/downloads)
|
||
- [:simple-linux: Linux](https://cryptomator.org/downloads)
|
||
- [:simple-flathub: Flathub](https://flathub.org/apps/details/org.cryptomator.Cryptomator)
|
||
|
||
Cryptomator uses AES-256 encryption to encrypt both files and filenames. Cryptomator cannot encrypt metadata such as access, modification, and creation timestamps, nor the number and size of files and folders.
|
||
|
||
Some Cryptomator cryptographic libraries have been [audited](https://community.cryptomator.org/t/has-there-been-a-security-review-audit-of-cryptomator/44) by Cure53. The scope of the audited libraries includes: [cryptolib](https://github.com/cryptomator/cryptolib), [cryptofs](https://github.com/cryptomator/cryptofs), [siv-mode](https://github.com/cryptomator/siv-mode) and [cryptomator-objc-cryptor](https://github.com/cryptomator/cryptomator-objc-cryptor). The audit did not extend to [cryptolib-swift](https://github.com/cryptomator/cryptolib-swift), which is a library used by Cryptomator for iOS.
|
||
|
||
Cryptomator's documentation details its intended [security target](https://docs.cryptomator.org/en/latest/security/security-target/), [security architecture](https://docs.cryptomator.org/en/latest/security/architecture/), and [best practices](https://docs.cryptomator.org/en/latest/security/best-practices/) for use in further detail.
|
||
|
||
### Picocrypt（ファイル）
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
|
||
**Picocrypt**は小さくシンプルな暗号化ツールで、最新の暗号化を提供します。 Picocryptは、セキュアなXChaCha20暗号とArgon2idキー派生機能を使用し、高レベルのセキュリティを提供します。 暗号化機能には、Go標準のx/cryptoモジュールを使用しています。
|
||
|
||
[:octicons-repo-16: Repository](https://github.com/HACKERALERT/Picocrypt){ .md-button .md-button--primary }
|
||
[:octicons-code-16:](https://github.com/HACKERALERT/Picocrypt){ .card-link title="ソースコード" }
|
||
[:octicons-heart-16:](https://opencollective.com/picocrypt){ .card-link title=貢献 }
|
||
|
||
??? ダウンロード
|
||
|
||
- [:simple-windows11: Windows](https://github.com/HACKERALERT/Picocrypt/releases)
|
||
- [:simple-apple: macOS](https://github.com/HACKERALERT/Picocrypt/releases)
|
||
- [:simple-linux: Linux](https://github.com/HACKERALERT/Picocrypt/releases)
|
||
|
||
### VeraCrypt（ディスク）
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
{ align=right }
|
||
|
||
**VeraCrypt** is a source-available freeware utility used for on-the-fly encryption. It can create a virtual encrypted disk within a file, encrypt a partition, or encrypt the entire storage device with pre-boot authentication.
|
||
|
||
[:octicons-home-16: Homepage](https://veracrypt.fr){ .md-button .md-button--primary }
|
||
[:octicons-info-16:](https://veracrypt.fr/en/Documentation.html){ .card-link title=Documentation}
|
||
[:octicons-code-16:](https://veracrypt.fr/code/){ .card-link title="Source Code" }
|
||
[:octicons-heart-16:](https://veracrypt.fr/en/Donation.html){ .card-link title=Contribute }
|
||
|
||
??? downloads
|
||
|
||
- [:simple-windows11: Windows](https://www.veracrypt.fr/en/Downloads.html)
|
||
- [:simple-apple: macOS](https://www.veracrypt.fr/en/Downloads.html)
|
||
- [:simple-linux: Linux](https://www.veracrypt.fr/en/Downloads.html)
|
||
|
||
VeraCryptは、終了したTrueCryptプロジェクトのフォークです。 開発者によると、セキュリティの改善が実装されており、最初のTrueCryptコード監査によって提起された問題が解決されています。
|
||
|
||
VeraCryptで暗号化する場合、異なる[ハッシュ関数](https://en.wikipedia.org/wiki/VeraCrypt#Encryption_scheme)から選択できます。 しかし、[SHA-512](https://en.wikipedia.org/wiki/SHA-512)**のみ**を選ぶことを推奨します。[AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)ブロック暗号以外を使うべきではありません。
|
||
|
||
Truecrypt has been [audited a number of times](https://en.wikipedia.org/wiki/TrueCrypt#Security_audits), and VeraCrypt has also been [audited separately](https://en.wikipedia.org/wiki/VeraCrypt#VeraCrypt_audit).
|
||
|
||
## OSのフルディスク暗号化
|
||
|
||
For encrypting the drive your operating system boots from, we generally recommend enabling the encryption software that comes with your operating system rather than using a third-party tool. This is because your operating system's native encryption tools often make use of OS and hardware-specific features like the [secure cryptoprocessor](https://en.wikipedia.org/wiki/Secure_cryptoprocessor) in your device to protect your computer against more advanced physical attacks. For secondary drives and external drives which you *don't* boot from, we still recommend using open-source tools like [VeraCrypt](#veracrypt-disk) over the tools below, because they offer additional flexibility and let you avoid vendor lock-in.
|
||
|
||
### BitLocker
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
|
||
**BitLocker** is the full volume encryption solution bundled with Microsoft Windows. The main reason we recommend it for encrypting your boot drive is because of its [use of TPM](https://docs.microsoft.com/en-us/windows/security/information-protection/tpm/how-windows-uses-the-tpm). ElcomSoft, a forensics company, has written about this feature in [Understanding BitLocker TPM Protection](https://blog.elcomsoft.com/2021/01/understanding-BitLocker-tpm-protection/).
|
||
|
||
[:octicons-info-16:](https://docs.microsoft.com/en-us/windows/security/information-protection/BitLocker/BitLocker-overview){ .card-link title=Documentation}
|
||
|
||
BitLocker is [only supported](https://support.microsoft.com/en-us/windows/turn-on-device-encryption-0c453637-bc88-5f74-5105-741561aae838) on Pro, Enterprise and Education editions of Windows. It can be enabled on Home editions provided that they meet the prerequisites.
|
||
|
||
??? example "Enabling BitLocker on Windows Home"
|
||
|
||
To enable BitLocker on "Home" editions of Windows, you must have partitions formatted with a [GUID Partition Table](https://en.wikipedia.org/wiki/GUID_Partition_Table) and have a dedicated TPM (v1.2, 2.0+) module. You may need to [disable the non-Bitlocker "Device encryption" functionality](https://discuss.privacyguides.net/t/enabling-bitlocker-on-the-windows-11-home-edition/13303/5) (which is inferior because it sends your recovery key to Microsoft's servers) if it is enabled on your device already before following this guide.
|
||
|
||
1. Open a command prompt and check your drive's partition table format with the following command. You should see "**GPT**" listed under "Partition Style":
|
||
|
||
```
|
||
powershell Get-Disk
|
||
```
|
||
|
||
2. Run this command (in an admin command prompt) to check your TPM version. You should see `2.0` or `1.2` listed next to `SpecVersion`:
|
||
|
||
```
|
||
powershell Get-WmiObject -Namespace "root/cimv2/security/microsofttpm" -Class WIN32_tpm
|
||
```
|
||
|
||
3. Access [Advanced Startup Options](https://support.microsoft.com/en-us/windows/advanced-startup-options-including-safe-mode-b90e7808-80b5-a291-d4b8-1a1af602b617). You need to reboot while pressing the F8 key before Windows starts and go into the *command prompt* in **Troubleshoot** → **Advanced Options** → **Command Prompt**.
|
||
|
||
4. Login with your admin account and type this in the command prompt to start encryption:
|
||
|
||
```
|
||
manage-bde -on c: -used
|
||
```
|
||
|
||
5. Close the command prompt and continue booting to regular Windows.
|
||
|
||
6. Open an admin command prompt and run the following commands:
|
||
|
||
```
|
||
manage-bde c: -protectors -add -rp -tpm
|
||
manage-bde -protectors -enable c:
|
||
manage-bde -protectors -get c: > %UserProfile%\Desktop\BitLocker-Recovery-Key.txt
|
||
```
|
||
|
||
!!! ヒント
|
||
|
||
Backup `BitLocker-Recovery-Key.txt` on your Desktop to a separate storage device. Loss of this recovery code may result in loss of data.
|
||
|
||
### FileVault
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
|
||
**FileVault** is the on-the-fly volume encryption solution built into macOS. FileVault is recommended because it [leverages](https://support.apple.com/guide/security/volume-encryption-with-filevault-sec4c6dc1b6e/web) hardware security capabilities present on an Apple silicon SoC or T2 Security Chip.
|
||
|
||
[:octicons-info-16:](https://support.apple.com/guide/mac-help/encrypt-mac-data-with-filevault-mh11785/mac){ .card-link title=Documentation}
|
||
|
||
We recommend storing a local recovery key in a secure place as opposed to using your iCloud account for recovery.
|
||
|
||
### Linux Unified Key Setup
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
|
||
**LUKS** is the default FDE method for Linux. It can be used to encrypt full volumes, partitions, or create encrypted containers.
|
||
|
||
[:octicons-home-16: Homepage](https://gitlab.com/cryptsetup/cryptsetup/-/blob/main/README.md){ .md-button .md-button--primary }
|
||
[:octicons-info-16:](https://gitlab.com/cryptsetup/cryptsetup/-/wikis/home){ .card-link title=Documentation}
|
||
[:octicons-code-16:](https://gitlab.com/cryptsetup/cryptsetup/){ .card-link title="Source Code" }
|
||
|
||
??? example "Creating and opening encrypted containers"
|
||
|
||
```
|
||
dd if=/dev/urandom of=/path-to-file bs=1M count=1024 status=progress
|
||
sudo cryptsetup luksFormat /path-to-file
|
||
```
|
||
|
||
|
||
#### Opening encrypted containers
|
||
We recommend opening containers and volumes with `udisksctl` as this uses [Polkit](https://en.wikipedia.org/wiki/Polkit). Most file managers, such as those included with popular desktop environments, can unlock encrypted files. Tools like [udiskie](https://github.com/coldfix/udiskie) can run in the system tray and provide a helpful user interface.
|
||
```
|
||
udisksctl loop-setup -f /path-to-file
|
||
udisksctl unlock -b /dev/loop0
|
||
```
|
||
|
||
!!! note "Remember to back up volume headers"
|
||
|
||
We recommend you always [back up your LUKS headers](https://wiki.archlinux.org/title/Dm-crypt/Device_encryption#Backup_and_restore) in case of partial drive failure. This can be done with:
|
||
|
||
```
|
||
cryptsetup luksHeaderBackup /dev/device --header-backup-file /mnt/backup/file.img
|
||
```
|
||
|
||
## Browser-based
|
||
|
||
Browser-based encryption can be useful when you need to encrypt a file but cannot install software or apps on your device.
|
||
|
||
### hat.sh
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
{ align=right }
|
||
|
||
**Hat.sh** is a web application that provides secure client-side file encryption in your browser. It can also be self-hosted and is useful if you need to encrypt a file but cannot install any software on your device due to organizational policies.
|
||
|
||
[:octicons-globe-16: Website](https://hat.sh){ .md-button .md-button--primary }
|
||
[:octicons-eye-16:](https://hat.sh/about/){ .card-link title="Privacy Policy" }
|
||
[:octicons-info-16:](https://hat.sh/about/){ .card-link title=Documentation}
|
||
[:octicons-code-16:](https://github.com/sh-dv/hat.sh){ .card-link title="Source Code" }
|
||
[:octicons-heart-16:](https://github.com/sh-dv/hat.sh#donations){ .card-link title="Donations methods can be found at the bottom of the website" }
|
||
|
||
## Command-line
|
||
|
||
Tools with command-line interfaces are useful for integrating [shell scripts](https://en.wikipedia.org/wiki/Shell_script).
|
||
|
||
### Kryptor
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
|
||
**Kryptor** is a free and open-source file encryption and signing tool that makes use of modern and secure cryptographic algorithms. It aims to be a better version of [age](https://github.com/FiloSottile/age) and [Minisign](https://jedisct1.github.io/minisign/) to provide a simple, easier alternative to GPG.
|
||
|
||
[:octicons-home-16: Homepage](https://www.kryptor.co.uk){ .md-button .md-button--primary }
|
||
[:octicons-eye-16:](https://www.kryptor.co.uk/features#privacy){ .card-link title="Privacy Policy" }
|
||
[:octicons-info-16:](https://www.kryptor.co.uk/tutorial){ .card-link title=Documentation}
|
||
[:octicons-code-16:](https://github.com/samuel-lucas6/Kryptor){ .card-link title="Source Code" }
|
||
[:octicons-heart-16:](https://www.kryptor.co.uk/#donate){ .card-link title=Contribute }
|
||
|
||
??? downloads
|
||
|
||
- [:simple-windows11: Windows](https://www.kryptor.co.uk)
|
||
- [:simple-apple: macOS](https://www.kryptor.co.uk)
|
||
- [:simple-linux: Linux](https://www.kryptor.co.uk)
|
||
|
||
### Tomb
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
|
||
**Tomb** is a command-line shell wrapper for LUKS. It supports steganography via [third-party tools](https://github.com/dyne/Tomb#how-does-it-work).
|
||
|
||
[:octicons-home-16: Homepage](https://www.dyne.org/software/tomb){ .md-button .md-button--primary }
|
||
[:octicons-info-16:](https://github.com/dyne/Tomb/wiki){ .card-link title=Documentation}
|
||
[:octicons-code-16:](https://github.com/dyne/Tomb){ .card-link title="Source Code" }
|
||
[:octicons-heart-16:](https://www.dyne.org/donate){ .card-link title=Contribute }
|
||
|
||
## OpenPGP
|
||
|
||
OpenPGP is sometimes needed for specific tasks such as digitally signing and encrypting email. PGP has many features and is [complex](https://latacora.micro.blog/2019/07/16/the-pgp-problem.html) as it has been around a long time. For tasks such as signing or encrypting files, we suggest the above options.
|
||
|
||
When encrypting with PGP, you have the option to configure different options in your `gpg.conf` file. We recommend staying with the standard options specified in the [GnuPG user FAQ](https://www.gnupg.org/faq/gnupg-faq.html#new_user_gpg_conf).
|
||
|
||
!!! tip "Use future defaults when generating a key"
|
||
|
||
When [generating keys](https://www.gnupg.org/gph/en/manual/c14.html) we suggest using the `future-default` command as this will instruct GnuPG use modern cryptography such as [Curve25519](https://en.wikipedia.org/wiki/Curve25519#History) and [Ed25519](https://ed25519.cr.yp.to/):
|
||
|
||
```bash
|
||
gpg --quick-gen-key alice@example.com future-default
|
||
```
|
||
|
||
### GNU Privacy Guard
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
|
||
**GnuPG** is a GPL-licensed alternative to the PGP suite of cryptographic software. GnuPG is compliant with [RFC 4880](https://tools.ietf.org/html/rfc4880), which is the current IETF specification of OpenPGP. The GnuPG project has been working on an [updated draft](https://datatracker.ietf.org/doc/draft-ietf-openpgp-crypto-refresh/) in an attempt to modernize OpenPGP. GnuPG is a part of the Free Software Foundation's GNU software project and has received major [funding](https://gnupg.org/blog/20220102-a-new-future-for-gnupg.html) from the German government.
|
||
|
||
[:octicons-home-16: Homepage](https://gnupg.org){ .md-button .md-button--primary }
|
||
[:octicons-eye-16:](https://gnupg.org/privacy-policy.html){ .card-link title="Privacy Policy" }
|
||
[:octicons-info-16:](https://gnupg.org/documentation/index.html){ .card-link title=Documentation}
|
||
[:octicons-code-16:](https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git){ .card-link title="Source Code" }
|
||
|
||
??? downloads
|
||
|
||
- [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=org.sufficientlysecure.keychain)
|
||
- [:simple-windows11: Windows](https://gpg4win.org/download.html)
|
||
- [:simple-apple: macOS](https://gpgtools.org)
|
||
- [:simple-linux: Linux](https://gnupg.org/download/index.html#binary)
|
||
|
||
### GPG4win
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
|
||
**GPG4win** is a package for Windows from [Intevation and g10 Code](https://gpg4win.org/impressum.html). It includes [various tools](https://gpg4win.org/about.html) that can assist you in using GPG on Microsoft Windows. The project was initiated and originally [funded by](https://web.archive.org/web/20190425125223/https://joinup.ec.europa.eu/news/government-used-cryptography) Germany's Federal Office for Information Security (BSI) in 2005.
|
||
|
||
[:octicons-home-16: Homepage](https://gpg4win.org){ .md-button .md-button--primary }
|
||
[:octicons-eye-16:](https://gpg4win.org/privacy-policy.html){ .card-link title="Privacy Policy" }
|
||
[:octicons-info-16:](https://gpg4win.org/documentation.html){ .card-link title=Documentation}
|
||
[:octicons-code-16:](https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpg4win.git;a=summary){ .card-link title="Source Code" }
|
||
[:octicons-heart-16:](https://gpg4win.org/donate.html){ .card-link title=Contribute }
|
||
|
||
??? downloads
|
||
|
||
- [:simple-windows11: Windows](https://gpg4win.org/download.html)
|
||
|
||
### GPG Suite
|
||
|
||
!!! note
|
||
|
||
We suggest [Canary Mail](email-clients.md#canary-mail) for using PGP with email on iOS devices.
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
|
||
**GPG Suite** provides OpenPGP support for [Apple Mail](email-clients.md#apple-mail) and macOS.
|
||
|
||
We recommend taking a look at their [First steps](https://gpgtools.tenderapp.com/kb/how-to/first-steps-where-do-i-start-where-do-i-begin-setup-gpgtools-create-a-new-key-your-first-encrypted-email) and [Knowledge base](https://gpgtools.tenderapp.com/kb) for support.
|
||
|
||
[:octicons-home-16: Homepage](https://gpgtools.org){ .md-button .md-button--primary }
|
||
[:octicons-eye-16:](https://gpgtools.org/privacy){ .card-link title="Privacy Policy" }
|
||
[:octicons-info-16:](https://gpgtools.tenderapp.com/kb){ .card-link title=Documentation}
|
||
[:octicons-code-16:](https://github.com/GPGTools){ .card-link title="Source Code" }
|
||
|
||
??? downloads
|
||
|
||
- [:simple-apple: macOS](https://gpgtools.org)
|
||
|
||
### OpenKeychain
|
||
|
||
!!! recommendation
|
||
|
||
{ align=right }
|
||
|
||
**OpenKeychain** is an Android implementation of GnuPG. It's commonly required by mail clients such as [K-9 Mail](email-clients.md#k-9-mail) and [FairEmail](email-clients.md#fairemail) and other Android apps to provide encryption support. Cure53 completed a [security audit](https://www.openkeychain.org/openkeychain-3-6) of OpenKeychain 3.6 in October 2015. Technical details about the audit and OpenKeychain's solutions can be found [here](https://github.com/open-keychain/open-keychain/wiki/cure53-Security-Audit-2015).
|
||
|
||
[:octicons-home-16: Homepage](https://www.openkeychain.org){ .md-button .md-button--primary }
|
||
[:octicons-eye-16:](https://www.openkeychain.org/help/privacy-policy){ .card-link title="Privacy Policy" }
|
||
[:octicons-info-16:](https://www.openkeychain.org/faq/){ .card-link title=Documentation}
|
||
[:octicons-code-16:](https://github.com/open-keychain/open-keychain){ .card-link title="Source Code" }
|
||
|
||
??? downloads
|
||
|
||
- [:simple-googleplay: Google Play](https://play.google.com/store/apps/details?id=org.sufficientlysecure.keychain)
|
||
|
||
## 基準
|
||
|
||
**私たちは、推薦するどのプロジェクトとも提携していません。**客観的に推薦できるよう、[標準となる基準](about/criteria.md)に加えて、一連の明確な要件を定めています。 プロジェクトを利用する前に、このリストをよく理解し、ご自身で調査を行って、そのプロジェクトがあなたにとって適切な選択かどうかをご確認ください。
|
||
|
||
!!! example "この項目は最近作成されました"
|
||
|
||
私たちは、サイトの各項目に定義された基準を確立することに取り組んでいます。この基準は変更される可能性があります。 私たちの基準について疑問がある場合は、[フォーラムで質問](https://discuss.privacyguides.net/latest)してください。また、ここに記載されていない場合でも、私たちがプロジェクトを推奨する際に、そうした事柄を考慮しなかったと仮定するのはお止めください。 プロジェクトを推奨する際に考慮され、議論される要素は多くあり、そのすべてを文書化する作業は現在進行中です。
|
||
|
||
### 最低要件
|
||
|
||
- クロスプラットフォームの暗号化アプリはオープンソースであること。
|
||
- ファイル暗号化アプリは、Linux、macOS、Windowsでの復号化をサポートするものであること。
|
||
- 外部ディスク暗号化アプリは、Linux、macOS、Windowsでの復号化をサポートするものであること。
|
||
- 内部（OS）ディスク暗号化アプリは、クロスプラットフォームであるか、OSにネイティブに組み込まれたものであること。
|
||
|
||
### 満たされることが望ましい基準
|
||
|
||
満たされることが望ましい基準には、このカテゴリーの完璧なプロジェクトに私たちが望むものを示しています。 私たちが推薦するプロジェクトは、この機能の一部または全部を含んでいないかもしれませんが、もし含んでいれば、このページで他のプロジェクトよりも上位にランクされるかもしれません。
|
||
|
||
- Operating System (FDE) encryption apps should utilize hardware security such as a TPM or Secure Enclave.
|
||
- File encryption apps should have first- or third-party support for mobile platforms.
|