Android Banking Biometric and KeyStore Hardening Brief

Role: Principal Android Security Architect specializing in hardware-backed cryptography and fintech mobile defense.

Context

• Target Financial Entity: {{institution_name}}
• Minimum Supported SDK & Baseline: Android API level {{target_android_api}}
• Core Authentication Requirement: {{auth_mechanism}}
• Regulatory and Compliance Baseline: {{compliance_standard}}
• Attack Vector Surface: {{threat_model_scope}}
• Cryptographic Provider & Key Storage Target: {{crypto_provider}}

Task

Produce an executive-ready Android Security Architecture Brief detailing the cryptographic signing pipeline, key attestation workflow, and biometric gating mechanisms required to secure transaction authorization against root compromise, memory dumping, and hooking frameworks.

Method

1. Analyze {{threat_model_scope}} to identify vulnerable surface points within the existing Android transaction flow.
2. Define the asymmetric key pair generation profile using {{crypto_provider}} with hardware-backed StrongBox verification where supported on {{target_android_api}}.
3. Formulate the explicit BiometricPrompt.CryptoObject binding logic for {{auth_mechanism}} to enforce biometric authorization for key usage without storing raw payload material.
4. Design the payload signing pipeline that consumes server nonces to eliminate replay attacks and satisfy {{compliance_standard}} requirements.
5. Detail the key attestation chain validation mechanism executed server-side to detect emulators, uncertified builds, and compromised keystores.
6. Specify fallback workflows and security degradation policies when hardware-isolated chips (TEE/StrongBox) are unavailable or invalidated.
7. Map dynamic runtime defense integration (SafetyNet/Play Integrity, tamper detection, and Frida hook protection) into the authentication lifecycle.

Constraints

• MUST mandate hardware-backed master key storage (StrongBox or TEE) and explicitly reject software-fallback key generation for signing.
• MUST NOT store private keys, biometric templates, or decrypted server nonces in SharedPreferences, SQLite, or plain process memory.
• All cryptographic signing algorithms must conform strictly to {{compliance_standard}} specifications.
• The brief must remain platform-accurate to Android API level {{target_android_api}} and above.

Output format

An executive security brief structured with these exact sections:

1. Cryptographic Key Lifecycle Architecture
2. Biometric Authentication & CryptoObject Pipeline
3. Attack Surface Defense Matrix (Minimum 4 threat vectors mapped to mitigations)
4. Hardware Attestation & Regulatory Compliance Validation (mapped to {{compliance_standard}}) Total length must not exceed 900 words.

Self-review

• Confirm all hardware Keystore specifications align with Android API {{target_android_api}} capabilities.
• Verify that biometric token validation relies on cipher-wrapped operations rather than boolean callbacks.
• Check that every mitigation addresses an explicit threat identified under {{threat_model_scope}}.