News for hackers. Stuff that matters.

A comment on Securing a Postgres Database. Parent comment

Re:Securing a Postgres Database by duckfang on Friday April 02, 2021 @03:49PM (#26675235)
You can put other machines with a highly restrictive set of network rules that allow data to cross inside the network and outside the network in very controlled ways.

Email is one such way.

[ Parent | on HN ]
Re:Securing a Postgres Database by capableweb on Friday April 02, 2021 @04:56PM (#26675900)
> Email is one such way.

I'm sorry but could you clarify? You mean that you monitor and/or collect data from hosts inside of a network via email somehow?

[ Parent | on HN ]
Re:Securing a Postgres Database by abhishekjha on Friday April 02, 2021 @05:15PM (#26676075)
I am curious. Most of the monitoring stacks include something like telegram/Prometheus to collect metrics and send to influxdb. How would you do this via email?
[ Parent | on HN ]
Re:Securing a Postgres Database by duckfang on Friday April 02, 2021 @07:41PM (#26677052)
Inside the he bastion network/VPC, there can be logging, monitoring, ad/kerb+openldap stuff to do the requisite thing. And your logging and monitoring can send trigger emails when they catch bad things.

Your inbox needs to be an automatable inbox, say controlled by bleeder or another flowengine. From there you can build a full messaging dashboard and have it done in something that could pass a very stringent audit.

[ Parent | on HN ]