How to upload database management?

[taejun-prestolabs]

Hello Team!
It seems I accidentally deleted all the rules.

It looks like I can upload rules in Seggins -> Scan history & database management, but where can I download the rules?

• UI/Frontend
• API/Backend
• Agent
• Deployment/YAMLs
• CI/CD Integration
• Other (specify)

Additional context
Add any other context or screenshots about the feature request here.

[ramanan-ravi]

Hello @taejun-prestolabs,

Please restart the console containers / pods.
It will download the rules.

[taejun-prestolabs]

Hello @ramanan-ravi
Thank you for your quick reply!

Which pods should I restart?

[taejun-prestolabs]

Sadly, Although I just restarted all pod(i deployed postgresql, neo4j to onprem), I can't view compliance

[taejun-prestolabs]

@ramanan-ravi

I have completely removed PostgreSQL and Neo4j, reinstalled them, and redeployed the Helm chart.
However, I still cannot see any compliance-related items.

Where is this rule triggered from, and how is it downloaded?

[gnmahanth]

@taejun-prestolabs

please check deepfence-console-scheduler and deepfence-console-worker logs for any errors related to database download ?

what version of ThreatMapper are you runing?

can you check if you have registered and have licence in settings section ? licence is required to download the databases

[taejun-prestolabs]

oh... sorry, �I didn't know i had to register the license.
thanks for you help..!

[taejun-prestolabs]

@gnmahanth

vulnerability db is not actually reflected even though it has been uploaded
threat mapper version is 2.5.1

I also confirmed that the vulnerability table is empty in neo4j db

[ramanan-ravi]

Hello @taejun-prestolabs Vulnerability nodes will be created as and when scans are done.
The vulnerability db is not ingested in neo4j right away. It is kept as sqlite locally.

[taejun-prestolabs]

Hi @ramanan-ravi

Although I can view vulnerability scan file in s3, I can't start vulnerability scan.
The error occurred even after restarting the scheduler, worker pods.

[taejun-prestolabs]

Hello, @ramanan-ravi @gnmahanth

Why doesn't grype db update run immediately when the worker pod runs?
Please let me know if there are any settings that are not needed.

worker pod entrypoint.sh code

#update vulnerability databae
if [ "$DEEPFENCE_MODE" == "worker" ]; then
echo "add cron job to update vulnerability database"
echo "vulnerability database update url $GRYPE_DB_UPDATE_URL"
# /usr/local/bin/grype db update
echo "0 */2 * * * export GRYPE_DB_UPDATE_URL=${GRYPE_DB_UPDATE_URL} && /usr/local/bin/grype db update" >> /etc/cron.d/crontab && chmod 0644 /etc/cron.d/crontab
/usr/sbin/cron
fi

Moreover, my pod dosen't have $XDG_CACHE_HOME env

It may be inconvenient, but please check...