mahanth

Results 26 issues of mahanth

Cloud scanner is unable to query for resources from GCP Steps to reproduce the behavior: 1. Deploy single account GCP cloud scanner using terrafrom 2. Run Cloud Compliance Scan, scan...

bug
needs-triage
v2

**Describe the bug** Run a Cloud compliance scan, download the scan results from scan page fails **Expected behavior** Xlsx format report download should be successful **Screenshots** ![image](https://github.com/deepfence/ThreatMapper/assets/22050509/3985311f-86c0-458a-95da-27b644ed7c90) **Logs** `scan_type is...

bug
needs-triage
area/ui-ux
v2

**Describe the bug** Image and resources are different, in side panel for a selected scan **Expected behavior** Resources should be a list of all the affected resources from the CVE...

bug
area/ui-ux
v2

In settings, There is a tab "vulnerability & Secret Management", this allows to clean up vulnerability and secret scan data, but there is no option to clean up Malware and...

bug

Update below components to latest version 1. grype latest version to support v5 vulnerability database 2. syft to include optimisation done in https://github.com/deepfence/syft/tree/optimise-resolver

enhancement
needs-triage

this is required to allow console to be scanned

enhancement

currently while trying to add harbor registry with self signed certificates we get this error ` ERROR:root: - HTTPSConnectionPool(host='143.244.128.178.nip.io', port=443): Max retries exceeded with url: /api/search?q= (Caused by SSLError(SSLCertVerificationError(1, '[SSL:...

bug
enhancement
needs-triage

merge vulnerability mapper from ThreatMapper to package-scanner making it easier to run vulnerability scans using [syft](https://github.com/anchore/syft) and [grype](https://github.com/anchore/grype) from a single place add option to run only sbom generation(syft) on...

enhancement
v2

Changes proposed in this pull request: - Replace fluent-bit by custom golang based shipper - reasons for this change 1. managing fluent bit for multiple arch with our output plugins...

Changes proposed in this pull request: - report error when results exceed 100k nodes while generating reports - add status_message filed in reports data - change reports struck in inprogress...