Re: [ADMIN] Postgres vs EnterpriseDB Vulnerability scans with Nessus - Mailing list pgsql-admin

From Joe Conway
Subject Re: [ADMIN] Postgres vs EnterpriseDB Vulnerability scans with Nessus
Date
Msg-id 314b48fc-ae41-eaee-3c54-49e1d3bc355b@joeconway.com
Whole thread Raw
In response to [ADMIN] Postgres vs EnterpriseDB Vulnerability scans with Nessus  ("Goldsmith, Christopher [ASM Research]" <christopher.goldsmith@asmr.com>)
Responses Re: [ADMIN] Postgres vs EnterpriseDB Vulnerability scans with Nessus  ("Goldsmith, Christopher [ASM Research]" <christopher.goldsmith@asmr.com>)
List pgsql-admin
On 06/30/2017 09:29 AM, Goldsmith, Christopher [ASM Research] wrote:
> We are using Nessus Version: 5.5.0 to run Vulnerability scans of our
> EnterpriseDB 9.5..x instances and Nessus is using up-to-date Postgres
> audit file/ policy / definitions.
>
> Is there anyone here that uses EnterpriseDB fork of Postgres and can
> confirm if the EnterpriseDB and Postgres are close enough that the
> results are valid and can be trusted.

EDB is a proprietary fork with unknown modifications (i.e. we on this
list don't have access to their source code), thus I think only EDB can
answer that question. You should be asking them.

Joe

--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development


Attachment

pgsql-admin by date:

Previous
From: Prateek Mahajan
Date:
Subject: [ADMIN] Postgres will not allow new connections, suspended process, waiting error
Next
From: Brian Farrell
Date:
Subject: Re: [ADMIN] Postgres will not allow new connections, suspendedprocess, waiting error