What it investigates
Some security weaknesses depend on how features, permissions, and application workflows interact. This mode explores those relationships and investigates how individual weaknesses could combine into a larger security impact.
The assessment stays within your saved target and scope. Available test accounts, documentation, and source context determine which areas CloudThinker can investigate.
When to use it
Choose this mode when you need a deeper understanding of an application’s security, particularly for:- Applications with several user roles or tenants.
- Business workflows where multiple actions affect permissions, data, or transactions.
- Important application changes that warrant a detailed assessment.
- Findings that suggest a broader attack path or need further investigation.
Prepare the application
Start with a registered Pentest app, verified ownership, and permission to run scans in your workspace.
Saved credentials do not confirm authenticated access. Review the run’s authentication results before treating protected areas as assessed.
Start the assessment
1
Open your app
Open the app in Cyber → Pentest, or Cyber → Overview when the app list appears there. Review its scope and access in Settings.
2
Choose the testing mode
Click Run pentest and select Deep dive under Testing intensity. For a new app, select it on the setup wizard’s Start step.For a manual run, you can optionally set Credit limit · Optional. Leave it blank for no per-run limit.
3
Review and launch
Review the target and destructive-testing warning, then confirm with Run Deep dive.Success state: the workbench opens with the run’s progress and findings.
A credit limit helps control testing spend but is not a hard spending cap. Completing work already in progress and preparing the report can take final usage above it. Clear an entered limit before scheduling.
Understand the results
Follow progress in the workbench, then review the evidence, impact, and remediation guidance for each finding. Focus on the demonstrated application behavior and the access required to reproduce it. Read authentication results and coverage limitations alongside the findings. Missing access, blocked areas, and incomplete checks limit the assessment; a run with no findings does not establish that an application is secure. Use Findings to prioritize remediation and request retesting after fixes. Use Reports to share the assessment and its limitations.Next steps
Triage security findings
Review evidence and prioritize remediation
Create Cyber reports
Share findings and assessment results