We have a newish Windows Server 2025 deploy of VBR v12 running latest patch and using PostgreSQL as the database.
CrowdStrike (antivirus/antimalware/etc) reports some vulnerabilities in the version of PostgreSQL and wants it updated.
Ideally I would wait for a "next VBR patch" and then hopefully it would update PostgreSQL for me.
I suppose I could try applying PostgreSQL patches myself, but I really would prefer to keep everything lined up version-wise.
Anyone else in the same boat? Recommended courses of action? How do y'all handle the competing priorities/risks?
-
Frosty
- Expert
- Posts: 210
- Liked: 46 times
- Joined: Dec 22, 2009 9:00 pm
- Full Name: Stephen Frost
- Contact:
-
karsten123
- Service Provider
- Posts: 664
- Liked: 165 times
- Joined: Apr 03, 2019 6:53 am
- Full Name: Karsten Meja
- Contact:
Re: VBR v12 with PostgreSQL -- security patching
you have to update postgresql by yourself
-
Gostev
- Chief Product Officer
- Posts: 32955
- Liked: 8085 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: VBR v12 with PostgreSQL -- security patching
Installable software for Microsoft Windows is self-managed so you have to patch everything yourself.
Our software appliance is fully managed so it's "set and forget" for you in terms of on-going patching and hardening, we take care of all of this for you.
Our software appliance is fully managed so it's "set and forget" for you in terms of on-going patching and hardening, we take care of all of this for you.
Who is online
Users browsing this forum: No registered users and 2 guests