Use Appdome to implement Federal Information Processing Standards Cryptographic Modules to mobile apps and protect mobile app data and network connections in seconds, no code or coding required.
Upgrade industry standard AES 256 Encryption to FIPS 140-2 Cryptography to protect mobile app data and network connections.
Use Appdome to build secure mobile apps that comply with FirstNet and NIST standards, in seconds, no code or coding required.
Use FIPS 140-2 cryptography to protect all the areas of the app, including the app sandbox, file system, secrets, strings, and more.
FIPS 140-2 Encryption is considered the security benchmark for sensitive but unclassified data, and critical for government agencies, and the contractors and vendors who work with them. Use Appdome to implement FIPS 140-2 Cryptographic Modules in any iOS and Android app, using only FIPS 140-2 approved checksum algorithms (SHA-1, SHA-224, SHA-256, SHA-384,SHA-512, SHA-512/224 and SHA-512/256). Ensure that the data connections used by the app, only use FIPS 140-2 compliant certificate and certificate-chain verification methods (X509_verify_cert). And in addition, guarantee that only FIPS 140-2 compliant encryption and hash algorithms will be used in the TLS handshake.
For mobile apps, the FIPS 140-2 Encryption guidelines specify the minimally acceptable security requirements for critical security parameters (CSP) including cryptographic modules, libraries, cipher suites, encryption algorithms, key strength, key derivation methods, and transmission protocols used by all cryptographic elements to secure data at rest, in use, and in transit. Make sure your mobile apps are FIPS compliant!
Appdome protects mobile app data with FIPS 140-2 Cryptography. Discrete blocks of data are encrypted and placed in a self-contained and segregated environment to isolate mobile app data from other resources. This prevents non-secure apps on the same device or different devices to decrypt and open this encrypted data. Appdome’s FIPS 140-2 implementation makes use of FIPS 140-2 compliant RNG to generate unique IVs (Initial Vectors), and the AES-256 block-cipher.
Appdome’s Trusted session inspection uses FIPS 140-2 compliant certificate and certificate-chain verification methods (X509_verify_cert). In addition, only FIPS 140-2 compliant encryption and hash algorithms will be used in the TLS handshake. Appdome uses only FIPS 140-2 compliant cryptographic functions when establishing TLS connections. When used in Session Hardening mode, the outward facing connection will be established using FIPS 140-2 cryptographic functions, thus making all outgoing TLS connections FIPS 140-2 compliant.
Encrypts keys, shared secrets, tokens, user preferences (username, email, contact info and other PII). With FIPS 140-2 enabled, Appdome uses FIPS 140-2 compliant RNG to generate unique IVs (Initial Vectors), and the AES-256 block-cipher.
Encrypts dynamic shared libraries, which contain native code stored inside an app package. For instance, if an attacker loads an Android app into a reversing tool, such as IDA or Hopper, Appdome ensures the attacker can’t access dynamic libraries even if they are extracted directly from app binary or device. Appdome’s Non-native code obfuscation makes use of FIPS 140-2 compliant RNG to generate unique IVs (Initial Vectors), and the AES-256 block-cipher.
Performs checksum validation to calculate a unique hash or fingerprint of binary data and assets and validates them at runtime. This prevents changes to the app, its resources, code, and configuration. Appdome’s Checksum validation computes and verifies only using FIPS 140-2 approved checksum algorithms (SHA-1, SHA-224, SHA-256, SHA-384, SHA-512, SHA-512/224 and SHA-512/256).
With Appdome's Certified Secure™ mobile app security certification, every mobile app release is certified-protected with the FIPS 140-2 encryption and other protections added to Android and iOS apps on Appdome. Certified Secure™ is the perfect complement to DevSecOps strategies. It can be used in "go, no-go" release meetings, compliance verification and to reduce reliance on code scanning services.
David Driegert, assistant program manager for MyNavy Portal
Mobile Applications at the Enterprise Information Systems PMW 240 Sea Warrior Program.
Security tips for mobile app developers
FIPS 140-2 compliance for mobile apps applies to multiple solutions involving mobile apps. As it relates to data at rest encryption, FIPS 140-2 cryptographic…
Appdome TOTALData Encryption is one of the cornerstones of our Mobile Security Suite. This mobile data encryption solution protects all application data coded, created, and used by the mobile…
Every year, OWASP releases reports on the top 10 most critical web and mobile application security risks, powerful awareness documents for application security that represent a broad consensus about the most…
Find detailed “step-by-step” instructions on using no-code Mobile Data Encryption for Android and iOS apps built in Android Studio, Java, Kotlin, C++, Ionic, React Native, Flutter, Cordova, Swift, Objective-C, Xcode, Xamarin, PhoneGap, and more. Learn how to protect any Android and iOS app from Data Breaches fast. Includes information on the patented technology that powers the Appdome mobile security platform, illustrated guides, mobile developer tips and more.
REDWOOD CITY OFFICE
3 Twin Dolphin Drive,
Suite 375 Redwood City, CA 94065
Phone: +1.650.567.6100
Mobile: +1.844.360.FUSE (3873)
Email: info@appdome.comISRAEL OFFICE
2 Eliezer Kaplan St,
12th floor Tel Aviv,
Israel 6473403
Phone: +972.3.720.7915
Email: info@appdome.com©2021 Appdome, Inc. All rights reserved. This Website requires the use of technical cookies and, with your consent, profiling, and third-party analytics to improve your experience. If you continue to use our Website, or by clicking any items of our Website, you agree to this.