Security Glossary

SAST (Static Application Security Testing) is a security testing technique that digs into an application’s source code or compiled files without ever actually running the application. It is designed to find vulnerabilities such as hardcoded keys, weak encryption, poor input validation, and misconfigurations early in the development process. SAST helps developers to find out and fix security bugs during the development phase by scanning applications' source code. This is called the shift-left approach, which makes securing an app faster and more cost-effective for organisations by identifying serious flaws early in the early SDLC phase. It helps identify threats like SQL injection before app release and gives developers quick feedback to resolve the issues and make a secure application. Finding issues at an early stage significantly lowers the cost of fixing them and prevents vulnerabilities from reaching the live production environment. CodeLock is an automated SAST tool from Bugsmirror that identifies more than 50 security vulnerabilities just by assessing the app binaries. It generates structured reports that prioritise risks based on severity and provide guidance on how to fix them. When integrated into the development pipeline, the tools help teams maintain secure coding practices as part of their regular workflow.

Screen overlay detection identifies when another app is displaying content over a running mobile app’s interface. Such overlays can hide or manipulate what the user sees on the screen and trick them into taking a malicious action. Malicious overlays can trick users into entering sensitive information like passwords, OTPs, or banking details. To prevent this, apps include screen overlay detection mechanisms that monitor system permissions and window behaviour to identify overlay activity. When detected, the app may block input fields, show warnings, or restrict certain actions. This is especially important for fintech apps, where overlay detection helps protect login screens and transactions from being compromised.

Screen share prevention restricts or blocks a mobile device’s ability to share its screen when a specific application is open. Screen sharing allows the display of the computer screen or phone screen to others remotely. Many apps prevent screen sharing with external applications or services during sensitive operations. This prevents the risk of data leakage. Applications may attempt to detect or restrict screen sharing using available platform controls to protect sensitive features or to mask critical information during such sessions. It is an essential check for application handling financial or personal data, account details, and transactions screen to prevent the screen share feature during their app operation.

Screenshot prevention helps security control that blocks users or other apps from capturing screenshots of sensitive screens within a mobile app. Screenshots can capture confidential information such as passwords, transaction details, or personal data, which may later be misused or shared. Applications use platform-level security flags to disable screenshot functionality when sensitive screens are active. Some implementations also prevent screen recording. These checks should be backed by a robust RASP solution which prevents attackers from disabling/bypassing such checks. In mobile apps, screenshots are prevented to protect their sensitive data, authentication data, reducing the risk of unauthorised sharing, saving or exposure.