Get access to immediate incident response assistance.
Eliminate active threats with 24/7 threat detection, investigation, and response.
Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.
Advance your cybersecurity program and get expert guidance where you need it most.
Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.
Prevent unauthorized access and exceed compliance requirements.
Stop email threats others miss and secure your organization against the #1 ransomware attack vector.
Prepare for the inevitable with 24/7 global breach response in-region and available on-site.
Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.
SSH to the policy server and check the timezone in postgresql:
Login to posgresql
psql -U finjan logs
logs=> show timezone;
TimeZone
----------
GMT
(1 row)
You will notice that the timezone in the database is different than the timezone configured on the policy server and scanners.
--------------------------------------------------------
To fix this you need to editpostgresql.conf (/opt/swg/configuration/data/postgresql/main/postgresql.conf).
Changed the two ‘GMT’ entries to‘US/Central’ or your desired timezone.
Restart postgresql (/etc/init.d/postgresql-9.3 restart). You should see the change immediately in the web logs. If you do not see an immediate change after restarting postgresql then the time zone format in postgresql.conf is not correct.
To contact Trustwave about this article or to request support: