Ask Learn Preview
Please sign in to use this experience.
Sign inThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Azure Database for PostgreSQL uses multiple layers of security to protect data. These layers include:
Azure Database for PostgreSQL encrypts data in transit and at rest. This topic is discussed in Unit 5.
Azure Database for PostgreSQL flexible server provides two networking options:
Note
When you create an Azure Database for PostgreSQL flexible server you select either Private access or Public access. Once your server has been created, you cannot change your network option.
Both options control access at the server level, not at the database or table level. Use PostgreSQL roles to grant or deny access to database, table, and other objects.
You also manage access to the server by creating firewall rules to allow connections only from known IP address ranges.
When you create an Azure Database for PostgreSQL server, you also create an admin account. This administrator account can be used to create more PostgreSQL roles. A role is a database user or group of users. Access to an Azure Database for PostgreSQL server is authenticated with a username, password, and the permissions granted or denied to the role.
Most access to an Azure Database for PostgreSQL server relies on passwords. However, it's possible to use SCRAM authentication, a secure password authentication protocol that can authenticate the client without revealing the user's cleartext password to the server. Salted Challenge Response Authentication Mechanism (SCRAM) is designed to make man-in-the-middle attacks more difficult.
To configure password encryption:
.
Having an issue? We can help!
Please sign in to use this experience.
Sign in