Page History
...
SQL Secure monitors different SQL Server versions installed on-premise or on cloud platforms.
| SQL Versions Windows Only | On-Premise | Microsoft Azure VM (IaaS) | Amazon EC2 (IaaS) | Microsoft Azure SQL Database (PaaS) | Amazon RDS (PaaS) |
|---|---|---|---|---|---|
| 2000 | X | ||||
| 2005 | X | X | |||
| 2008 R2 | X | X | X | X | |
| 2012 SP1 | X | X | X | X | |
| 2016 | X | X | X | X | |
| 2017 | X | X | X | X | |
| 2019 | X | X | X | X | |
| Azure SQL Database V12 | X |
Collector permission requirements
The following requirements are necessary for the SQL Secure Collector to access the SQL Server instances you want to audit. During install, you can input credentials for a Windows user account or SQL Server login.
| Type | Requirement |
|---|---|
| Windows permissions | A Windows user account that has local administrator permissions. |
| SQL Server privileges | A Windows user account that is a member of the sysadmin fixed server role on the SQL Server instance. |
Port requirements
SQL Secure uses the default ports opened by the Windows operating system for local and remote communications. To learn about Windows port assignments, see
| Newtab2 | ||||
|---|---|---|---|---|
|
| Newtab2 | ||||
|---|---|---|---|---|
|
| Type | Requirement |
|---|---|
| SQL Server Object Permissions and configuration collection | Port 1433 (or the configured SQL instance port for the audited instance) |
| Windows file system and registry permissions collection | Port 135 (RPC connectivity) |