| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | "Goldsmith, Christopher [ASM Research]" <christopher(dot)goldsmith(at)asmr(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Postgres vs EnterpriseDB Vulnerability scans with Nessus |
| Date: | 2017-06-30 20:45:24 |
| Message-ID: | 314b48fc-ae41-eaee-3c54-49e1d3bc355b@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brian Farrell | 2017-06-30 20:46:06 | Re: Postgres will not allow new connections, suspended process, waiting error |
| Previous Message | Prateek Mahajan | 2017-06-30 20:39:29 | Postgres will not allow new connections, suspended process, waiting error |