Threat level
—
Loading posture…
Critical
–
Open, unresolved
High
–
Open, unresolved
Medium
–
Open, unresolved
SLA Overdue
–
Past deadline
Known-exploited
–
On CISA KEV
Active findings — last 30 days
Severity mix
Findings by source
Scan activity
OWASP Top 10 (2021)
ASVS 4.0 coverage
| Incident | Pri | Severity | Title | Source | Location | Status |
|---|
Single
Bulk paste
CSV upload
Discover
Targets
| Name | Kind | Tags | Findings | Scans | Actions |
|---|
Total assets
–
Under management
Internet-facing
–
Domains, subdomains, IPs
At risk
–
Facing assets with med+ findings
Asset types
–
Distinct kinds
Assets by risk
| Asset | Kind | Exposure | Risk | Findings | Overdue | Tags |
|---|
Scan a mobile app
Upload an Android
.apk or iOS .ipa. MobSF runs static analysis (code, manifest, network-security config, certificate) and the results flow into Findings with OWASP/ASVS tags like every other scan.Mobile apps
| App | Scans | Findings | Actions |
|---|
AWS account
–
region
Cloud findings
–
Prowler + GuardDuty
GuardDuty
–
Runtime threats
Config posture — Prowler
Scans your AWS account against hundreds of CIS/best-practice checks (IAM, S3, security groups, encryption). Findings are OCSF-normalized into the register.
Scan one region at a time — Prowler holds every discovered resource in memory, so account-wide runs can exhaust it.
Runtime threats — GuardDuty
Pulls active GuardDuty detections — compromised credentials, crypto-mining, recon, exfiltration. The "someone is attacking us now" signal that config scans can't see.
| Incident | Sev | Pri | Title | OWASP | Location | Status |
|---|
Organization
–
GitHub org
Alert findings
–
Code scanning + Dependabot
Last sync
–
Pulled from GitHub
GitHub security alerts
Pulls org-wide code-scanning (CodeQL) and Dependabot alerts into the unified register, deduplicated and OWASP-tagged like every other source. Uses your
GITHUB_TOKEN (or a GitHub App).Click Load repos to list repositories in your org.
| Incident | Sev | Pri | Title | OWASP | Location | Status |
|---|
Run a scan
Pick a target — Shield suggests the scanners that fit it.
1
2
Import an existing report
Continuous monitoring schedule Scheduler →
Baseline coverage that runs without configuration. Set the cadence here;
build anything more specific — a single target, one scanner, a UTC window —
in the Scheduler.
Remediation SLA policy
Days to remediate by severity. Applies to findings created after a change; info has no SLA.
Scan history
| # | Target | Source | Status | Started | Duration | Findings |
|---|
Select a discussion.
Assigned to me
–
Open or triaged in your queue
Overdue
–
Past SLA deadline
Under review
–
Your findings, disputed
Waiting on me
–
Disputes you can decide
Assigned to me 0
Awaiting my review 0
Raised by me 0
| ID | Severity | Title | Priority▼ | Status | SLA | Assigned | Actions |
|---|
| Incident | Sev | Pri | Title | Source | Owner | Age | SLA | Status |
|---|
Generate report
Branded PDF with the MapUp logo, severity charts, and a findings table. Retained on the server and shareable via link. A tag report aggregates findings across every target carrying that tag.
Saved reports
| Target | Generated | Formats | Actions |
|---|
New schedule
and
Schedules
| Name | Scope | Scanners | Cadence | Last run | Next run | Actions |
|---|
My profile
Change password
Two-factor authentication (MFA)