Performing Cryptographic Audit Of Application

Performing Cryptographic Audit of Application

Overview

A cryptographic audit systematically reviews an application's use of cryptographic primitives, protocols, and key management to identify vulnerabilities such as weak algorithms, insecure modes, hardcoded keys, insufficient entropy, and protocol misconfigurations. This skill covers building an automated crypto audit tool that scans Python and configuration files for common cryptographic weaknesses.

When to Use

Trigger phrases:

• "performing cryptographic audit of application"

• "A cryptographic audit systematically reviews an application's use of cryptograph"

• When conducting security assessments that involve performing cryptographic audit of application

• When following incident response procedures for related security events

• When performing scheduled security testing or auditing activities

• When validating security controls through hands-on testing

Prerequisites

• Familiarity with cryptography concepts and tools
• Access to a test or lab environment for safe execution
• Python 3.8+ with required dependencies installed
• Appropriate authorization for any testing activities

Objectives

• Detect usage of deprecated algorithms (MD5, SHA-1, DES, RC4)
• Identify insecure cipher modes (ECB) and padding schemes
• Find hardcoded keys, passwords, and secrets in source code
• Verify TLS/SSL configuration strength
• Check key derivation function parameters
• Validate random number generator usage
• Produce a structured audit report with findings and remediation

Key Concepts

This section covers key concepts for performing cryptographic audit of application.

• Ensure all prerequisites are met before proceeding
• Follow the documented workflow steps in sequence
• Record results and any anomalies encountered during this phase

Cryptographic Weakness Categories

Security Considerations

• Review both application code and configuration files
• Check third-party dependencies for known crypto vulnerabilities
• Verify certificates and TLS configurations on deployed servers
• Ensure secrets are loaded from environment variables or vaults
• Review key storage and rotation practices

Validation Criteria

• Scanner detects all injected test weaknesses
• MD5/SHA-1 usage for security purposes is flagged
• ECB mode usage is flagged
• Hardcoded keys/passwords are detected
• Weak KDF parameters are identified
• Report includes severity, location, and remediation
• False positive rate is below 10%

When NOT to Use

• You don't have explicit written authorization to test
• Task is about defense/detection, not offense (use detection skills)
• You need to implement security controls (use implementing-* skills)
• Task requires compliance auditing (use auditing-* skills)
• You're investigating an incident (use incident response skills)
• Target is out of scope for your engagement
• Task is about vulnerability scanning only (use scanning tools)

Red Flags

• Performing actions without explicit written authorization from the asset owner
• Testing against production systems without a defined scope and rules of engagement
• Treating compliance checklists as security guarantees rather than minimum baselines
• Failing to document exceptions and risk acceptance decisions
• Relying on point-in-time audits instead of continuous monitoring

Verification

• All steps executed successfully against a test environment before production use
• Output documented with screenshots or logs demonstrating expected behavior
• Results validated against known-good baselines or reference implementations
• Documentation complete enough for another analyst to reproduce findings

Process

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}

1. Analyze the task requirements
2. Apply domain expertise
3. Verify output quality

Anti-Rationalization Table