Skip to Content
ASCADocs

Concepts

The main objects used to organise an application security review in ASCA.

Account and workspace

Your account identifies you when you sign in. A workspace groups a team's applications, scans, findings and members. Select the intended workspace before working with an application or sharing results.

Members have roles that determine the actions available to them. Ask a workspace administrator if you need access or cannot perform an action.

APK and application version

An APK is an Android application package. A review applies to the submitted build; findings from one version do not automatically describe a later version. Keep the package name and version alongside your review notes.

Scan

A scan is an analysis run against an application build. Its status shows whether the run is waiting, running or finished. An interrupted or failed scan is not evidence that the application has no vulnerabilities.

Scan execution and Google Play import are not yet enabled during the private rollout. The quickstart describes what you can prepare now.

Finding and report

A finding describes a potential security issue, its evidence, impact and suggested remediation. A report brings the results of a review together.

Automated analysis can miss issues or produce false positives. Review the evidence and validate a fix in the relevant application version. A scan with no findings does not establish that an application is secure.

On this page