Microsoft Purview-可以使用数据库监视防火墙规则吗?
我一直在寻找一种最好的解决方案,最好是本机,以监视在不同Azure SQL服务器上托管的多个Azure SQL数据库中对防火墙规则的更改。尽管Azure政策最初似乎适合该法案,但后来事实证明这是可以的,这也仅适用于Azure SQL服务器。今天,我遇到 purview ,作为数据治理解决方案展示。我设法设置了一个Purview帐户,并连接了一个数据库以进行扫描。扫描规则没有提供太多的可自定义性,对我来说还不清楚它的实际扫描 - 它只是在数据库中寻找流浪IP地址吗?我也无法从结果中解密太多用例。
有什么办法可以使用purview实现我的目标?我也对实现这一目标的其他建议开放。
I have been looking for a solution, preferably native, to monitor changes to firewall rules across multiple Azure SQL databases hosted on different Azure SQL servers. While Azure Policy seemed to fit the bill initially, it later turned out to be okayish, that too only for Azure SQL servers. Today, I came across Purview, showcased as a data governance solution. I managed to set up a Purview account and hooked up a database to be scanned. The scan rules didn't offer much customizability and it wasn't clear to me what it actually scans - does it just look for stray IP addresses across the database? I could not decipher much from the results for my use case either.
Is there any way to achieve my objective using Purview? I am also open to other suggestions to achieve it.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
Purview不是正确的工具。最好的选择是使用 azure Monitor 创建警报创建,更新或删除规则时。创建新警报时,选择以下信号:
Purview is not the right tool for this. Your best bet is using Azure Monitor to create an alert when rules are created, updated or deleted. When creating a new alert choose the following signal(s):
Azure功能以及逻辑应用程序原来是一个很好的解决方案。基于活动日志警报触发的逻辑应用程序又激活了Azure函数,该功能使用PowerShell脚本仅维护SQL Server上批准的FireWall规则集。是的,这不在数据库内,并检查那里定义的防火墙规则,但是出于我的目的,事实证明这足够了。
我从此来源。
Azure Functions coupled with logic apps turned out to be a good solution for this. The logic app which gets triggered based on an activity log alert in turn activates an Azure Function which uses a PowerShell script to maintain only the approved set of firewall rules on an SQL Server. Yes, this does not go inside the databases and check for firewall rules defined there, but for my purpose, this turned out to be sufficient.
I got the above inputs from this source.