pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedPostgres vs EnterpriseDB Vulnerability scans with Nessus
3+ messages / 2 participants
[nested] [flat]
* Postgres vs EnterpriseDB Vulnerability scans with Nessus
@ 2017-06-30 16:29 Goldsmith, Christopher [ASM Research] <christopher.goldsmith@asmr.com>
2017-06-30 20:45 ` Re: Postgres vs EnterpriseDB Vulnerability scans with Nessus Joe Conway <mail@joeconway.com>
0 siblings, 1 reply; 3+ messages in thread
From: Goldsmith, Christopher [ASM Research] @ 2017-06-30 16:29 UTC (permalink / raw)
To: pgsql-admin
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.
Our need for all this is to meet Federal audit requirements.
The information contained in this message may be privileged and/or confidential and protected from disclosure. If the reader of this message is not the intended recipient or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to this message and deleting the material from any computer.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Postgres vs EnterpriseDB Vulnerability scans with Nessus
2017-06-30 16:29 Postgres vs EnterpriseDB Vulnerability scans with Nessus Goldsmith, Christopher [ASM Research] <christopher.goldsmith@asmr.com>
@ 2017-06-30 20:45 ` Joe Conway <mail@joeconway.com>
2017-07-03 12:47 ` Re: Postgres vs EnterpriseDB Vulnerability scans with Nessus Goldsmith, Christopher [ASM Research] <christopher.goldsmith@asmr.com>
0 siblings, 1 reply; 3+ messages in thread
From: Joe Conway @ 2017-06-30 20:45 UTC (permalink / raw)
To: Goldsmith, Christopher [ASM Research] <christopher.goldsmith@asmr.com>; 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
Attachments:
signature.asc (application/pgp-signature, 818B) download
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Postgres vs EnterpriseDB Vulnerability scans with Nessus
2017-06-30 16:29 Postgres vs EnterpriseDB Vulnerability scans with Nessus Goldsmith, Christopher [ASM Research] <christopher.goldsmith@asmr.com>
2017-06-30 20:45 ` Re: Postgres vs EnterpriseDB Vulnerability scans with Nessus Joe Conway <mail@joeconway.com>
@ 2017-07-03 12:47 ` Goldsmith, Christopher [ASM Research] <christopher.goldsmith@asmr.com>
0 siblings, 0 replies; 3+ messages in thread
From: Goldsmith, Christopher [ASM Research] @ 2017-07-03 12:47 UTC (permalink / raw)
To: Joe Conway <mail@joeconway.com>; pgsql-admin
I also have the same question in via a support case with EDB was asking here to cover all bases
-----Original Message-----
From: Joe Conway [mailto:mail@joeconway.com]
Sent: Friday, June 30, 2017 3:45 PM
To: Goldsmith, Christopher [ASM Research] <christopher.goldsmith@asmr.com>; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Postgres vs EnterpriseDB Vulnerability scans with Nessus
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 - https://linkprotect.cudasvc.com/url?a=http://crunchydata.com&c=E,1,O5gz5x1HnTh4y__e0q4okkLL0WLU8...
PostgreSQL Support for Secure Enterprises Consulting, Training, & Open Source Development
The information contained in this message may be privileged and/or confidential and protected from disclosure. If the reader of this message is not the intended recipient or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by replying to this message and deleting the material from any computer.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2017-07-03 12:47 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2017-06-30 16:29 Postgres vs EnterpriseDB Vulnerability scans with Nessus Goldsmith, Christopher [ASM Research] <christopher.goldsmith@asmr.com>
2017-06-30 20:45 ` Joe Conway <mail@joeconway.com>
2017-07-03 12:47 ` Goldsmith, Christopher [ASM Research] <christopher.goldsmith@asmr.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox