Best Practices in Security with PostgreSQL

The webinar reviews a multi-layered framework for PostgreSQL security, with a deeper focus on limiting access to the database and data, as well as securing the data. Using the popular AAA (Authentication, Authorization, Auditing) framework, we will cover:
- Best practices for authentication (trust, certificate, MD5, Scram, etc).
- Advanced approaches, such as password profiles.
- Deep dive of authorization and data access control for roles, database objects (tables etc), view usage, row level security and data redaction.
- Auditing, encryption and SQL injection attack prevention.
-------------------------------------------------------------------------------
For more #webinars​​​​​, visit okt.to/FMH5mq
Download free #PostgreSQL​​​​​ whitepapers: okt.to/uVzUTZ
Read our #Postgres​​​​​ Blog okt.to/A0Uy2h
Follow us on Facebook at okt.to/kiV12G
Follow us on Twitter at okt.to/6E3XDS
Follow us on LinkedIn at okt.to/svStHa
Reach us via email at [e-mail]

[@cybrflash]

Somehow I've never heard of, or maybe never paid attention to EDB. No longer - you have a new fan! This webinar was amazing!! Thank you so much for the very thorough, in-depth and detailed PostgreSQL Security deep dive!

[@rajatbanik123]

EDB Postgres is one of the best database in the world as per stack overflow survey

[@atharfahad7337]

Perfect Dave..

[@techmaniacc6065]

Thanks

[@Funkfreed]

for RLS been trying to find out how to do the other way around wherein admin can read all users with the same company id I am getting an infinite recursion due to the relation

[@xiaokourou]

Had a similar problem. Be careful that the values in with check and using will be different (new row, old row). What also helped me was moving the check into a function