Home/Compliance
owasp-mobile-2024

owasp-mobile-2024. Security Controls

10 controls · cross-mapped to ATT&CK techniques
Translate between regulatory language and what attackers actually do. Each control maps to MITRE ATT&CK techniques; open a control to see those techniques and whether we hold detection coverage for them.
10
Total controls
0%
Detection coverage
0
Covered controls
10
Coverage gaps
▤ Export audit (CSV) Coverage report Self-assessment Show gaps only
▶ Check your own detection coverage

Paste the ATT&CK technique IDs you have Sigma/YARA rules for (one per line, e.g. T1059, T1190). The controls below will update to show YOUR coverage instead of ours.

Red team insight A owasp-mobile-2024 compliant org should have detection for the green-tagged techniques below. Controls showing no technique coverage are likely blind spots. Use gaps view to enumerate unmonitored attack paths.

Controls

10 shown of 10
Use of weak or improperly implemented cryptographic algorithms can compromise the confidentiality and integrity of mobile application data.
family M framework owasp-mobile-2024
Hardcoded credentials, insecure credential transmission, and other improper credential handling practices.
family M framework owasp-mobile-2024
Mobile applications often rely on third-party libraries, SDKs, and APIs. Inadequate supply chain security can lead to compromised dependencies.
family M framework owasp-mobile-2024
Weak authentication and authorization mechanisms in mobile applications can lead to unauthorized access.
family M framework owasp-mobile-2024
Failure to properly validate user inputs and output sanitization can lead to injection attacks and data corruption.
family M framework owasp-mobile-2024
Mobile applications often communicate with servers over networks. Insecure communication channels can expose data to interception.
family M framework owasp-mobile-2024
Failure to implement adequate privacy controls can result in unauthorized collection or exposure of personal data.
family M framework owasp-mobile-2024
Mobile applications can be reverse-engineered if not properly protected, exposing intellectual property and security mechanisms.
family M framework owasp-mobile-2024
Misconfigured permissions, default settings, and insecure storage locations can compromise mobile application security.
family M framework owasp-mobile-2024
Storing sensitive data insecurely on mobile devices can lead to unauthorized access if the device is compromised.
family M framework owasp-mobile-2024
Showing 1-10 of 10
Vulnerabilities
CISA KEV catalog
CWE weaknesses
CAPEC attack patterns
Package vulnerabilities
Threat intelligence
Threat actors
Tools & malware
ATT&CK techniques
IOCs
Detection & defense
Sigma rules
YARA rules
Atomic Red Team tests
D3FEND countermeasures
Compliance
NIST 800-53
ISO 27001:2022
SOC 2 TSC
PCI-DSS v4.0
CIS Controls v8.1
About
All capabilities
Live statistics
Data sources
Privacy policy
Terms of service
threatengine.sh  ·  Open-source threat intelligence platform  ·  100+ authoritative sources  ·  Every fact traces to its origin