// Copyright (c) Microsoft Corporation. All rights reserved.
// Licensed under the MIT License.

// <auto-generated/>

#nullable disable

using System;
using System.Collections.Generic;
using Azure.Core;

namespace Azure.ResourceManager.Sql.Models
{
    /// <summary> An extended server blob auditing policy. </summary>
    public partial class ExtendedServerBlobAuditingPolicy : Resource
    {
        /// <summary> Initializes a new instance of ExtendedServerBlobAuditingPolicy. </summary>
        public ExtendedServerBlobAuditingPolicy()
        {
            AuditActionsAndGroups = new ChangeTrackingList<string>();
        }

        /// <summary> Initializes a new instance of ExtendedServerBlobAuditingPolicy. </summary>
        /// <param name="id"> Resource ID. </param>
        /// <param name="name"> Resource name. </param>
        /// <param name="type"> Resource type. </param>
        /// <param name="predicateExpression"> Specifies condition of where clause when creating an audit. </param>
        /// <param name="state"> Specifies the state of the policy. If state is Enabled, storageEndpoint or isAzureMonitorTargetEnabled are required. </param>
        /// <param name="storageEndpoint"> Specifies the blob storage endpoint (e.g. https://MyAccount.blob.core.windows.net). If state is Enabled, storageEndpoint or isAzureMonitorTargetEnabled is required. </param>
        /// <param name="storageAccountAccessKey">
        /// Specifies the identifier key of the auditing storage account.
        /// 
        /// If state is Enabled and storageEndpoint is specified, not specifying the storageAccountAccessKey will use SQL server system-assigned managed identity to access the storage.
        /// 
        /// Prerequisites for using managed identity authentication:
        /// 
        /// 1. Assign SQL Server a system-assigned managed identity in Azure Active Directory (AAD).
        /// 
        /// 2. Grant SQL Server identity access to the storage account by adding &apos;Storage Blob Data Contributor&apos; RBAC role to the server identity.
        /// 
        /// For more information, see [Auditing to storage using Managed Identity authentication](https://go.microsoft.com/fwlink/?linkid=2114355).
        /// </param>
        /// <param name="retentionDays"> Specifies the number of days to keep in the audit logs in the storage account. </param>
        /// <param name="auditActionsAndGroups">
        /// Specifies the Actions-Groups and Actions to audit.
        /// 
        /// 
        /// 
        /// The recommended set of action groups to use is the following combination - this will audit all the queries and stored procedures executed against the database, as well as successful and failed logins:
        /// 
        /// 
        /// 
        /// BATCH_COMPLETED_GROUP,
        /// 
        /// SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP,
        /// 
        /// FAILED_DATABASE_AUTHENTICATION_GROUP.
        /// 
        /// 
        /// 
        /// This above combination is also the set that is configured by default when enabling auditing from the Azure portal.
        /// 
        /// 
        /// 
        /// The supported action groups to audit are (note: choose only specific groups that cover your auditing needs. Using unnecessary groups could lead to very large quantities of audit records):
        /// 
        /// 
        /// 
        /// APPLICATION_ROLE_CHANGE_PASSWORD_GROUP
        /// 
        /// BACKUP_RESTORE_GROUP
        /// 
        /// DATABASE_LOGOUT_GROUP
        /// 
        /// DATABASE_OBJECT_CHANGE_GROUP
        /// 
        /// DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP
        /// 
        /// DATABASE_OBJECT_PERMISSION_CHANGE_GROUP
        /// 
        /// DATABASE_OPERATION_GROUP
        /// 
        /// DATABASE_PERMISSION_CHANGE_GROUP
        /// 
        /// DATABASE_PRINCIPAL_CHANGE_GROUP
        /// 
        /// DATABASE_PRINCIPAL_IMPERSONATION_GROUP
        /// 
        /// DATABASE_ROLE_MEMBER_CHANGE_GROUP
        /// 
        /// FAILED_DATABASE_AUTHENTICATION_GROUP
        /// 
        /// SCHEMA_OBJECT_ACCESS_GROUP
        /// 
        /// SCHEMA_OBJECT_CHANGE_GROUP
        /// 
        /// SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP
        /// 
        /// SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP
        /// 
        /// SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP
        /// 
        /// USER_CHANGE_PASSWORD_GROUP
        /// 
        /// BATCH_STARTED_GROUP
        /// 
        /// BATCH_COMPLETED_GROUP
        /// 
        /// 
        /// 
        /// These are groups that cover all sql statements and stored procedures executed against the database, and should not be used in combination with other groups as this will result in duplicate audit logs.
        /// 
        /// 
        /// 
        /// For more information, see [Database-Level Audit Action Groups](https://docs.microsoft.com/en-us/sql/relational-databases/security/auditing/sql-server-audit-action-groups-and-actions#database-level-audit-action-groups).
        /// 
        /// 
        /// 
        /// For Database auditing policy, specific Actions can also be specified (note that Actions cannot be specified for Server auditing policy). The supported actions to audit are:
        /// 
        /// SELECT
        /// 
        /// UPDATE
        /// 
        /// INSERT
        /// 
        /// DELETE
        /// 
        /// EXECUTE
        /// 
        /// RECEIVE
        /// 
        /// REFERENCES
        /// 
        /// 
        /// 
        /// The general form for defining an action to be audited is:
        /// 
        /// {action} ON {object} BY {principal}
        /// 
        /// 
        /// 
        /// Note that &lt;object&gt; in the above format can refer to an object like a table, view, or stored procedure, or an entire database or schema. For the latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are used, respectively.
        /// 
        /// 
        /// 
        /// For example:
        /// 
        /// SELECT on dbo.myTable by public
        /// 
        /// SELECT on DATABASE::myDatabase by public
        /// 
        /// SELECT on SCHEMA::mySchema by public
        /// 
        /// 
        /// 
        /// For more information, see [Database-Level Audit Actions](https://docs.microsoft.com/en-us/sql/relational-databases/security/auditing/sql-server-audit-action-groups-and-actions#database-level-audit-actions).
        /// </param>
        /// <param name="storageAccountSubscriptionId"> Specifies the blob storage subscription Id. </param>
        /// <param name="isStorageSecondaryKeyInUse"> Specifies whether storageAccountAccessKey value is the storage&apos;s secondary key. </param>
        /// <param name="isAzureMonitorTargetEnabled">
        /// Specifies whether audit events are sent to Azure Monitor.
        /// 
        /// In order to send the events to Azure Monitor, specify &apos;state&apos; as &apos;Enabled&apos; and &apos;isAzureMonitorTargetEnabled&apos; as true.
        /// 
        /// 
        /// 
        /// When using REST API to configure auditing, Diagnostic Settings with &apos;SQLSecurityAuditEvents&apos; diagnostic logs category on the database should be also created.
        /// 
        /// Note that for server level audit you should use the &apos;master&apos; database as {databaseName}.
        /// 
        /// 
        /// 
        /// Diagnostic Settings URI format:
        /// 
        /// PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
        /// 
        /// 
        /// 
        /// For more information, see [Diagnostic Settings REST API](https://go.microsoft.com/fwlink/?linkid=2033207)
        /// 
        /// or [Diagnostic Settings PowerShell](https://go.microsoft.com/fwlink/?linkid=2033043)
        /// 
        /// .
        /// </param>
        /// <param name="queueDelayMs">
        /// Specifies the amount of time in milliseconds that can elapse before audit actions are forced to be processed.
        /// 
        /// The default minimum value is 1000 (1 second). The maximum is 2,147,483,647.
        /// </param>
        internal ExtendedServerBlobAuditingPolicy(string id, string name, string type, string predicateExpression, BlobAuditingPolicyState? state, string storageEndpoint, string storageAccountAccessKey, int? retentionDays, IList<string> auditActionsAndGroups, Guid? storageAccountSubscriptionId, bool? isStorageSecondaryKeyInUse, bool? isAzureMonitorTargetEnabled, int? queueDelayMs) : base(id, name, type)
        {
            PredicateExpression = predicateExpression;
            State = state;
            StorageEndpoint = storageEndpoint;
            StorageAccountAccessKey = storageAccountAccessKey;
            RetentionDays = retentionDays;
            AuditActionsAndGroups = auditActionsAndGroups;
            StorageAccountSubscriptionId = storageAccountSubscriptionId;
            IsStorageSecondaryKeyInUse = isStorageSecondaryKeyInUse;
            IsAzureMonitorTargetEnabled = isAzureMonitorTargetEnabled;
            QueueDelayMs = queueDelayMs;
        }

        /// <summary> Specifies condition of where clause when creating an audit. </summary>
        public string PredicateExpression { get; set; }
        /// <summary> Specifies the state of the policy. If state is Enabled, storageEndpoint or isAzureMonitorTargetEnabled are required. </summary>
        public BlobAuditingPolicyState? State { get; set; }
        /// <summary> Specifies the blob storage endpoint (e.g. https://MyAccount.blob.core.windows.net). If state is Enabled, storageEndpoint or isAzureMonitorTargetEnabled is required. </summary>
        public string StorageEndpoint { get; set; }
        /// <summary>
        /// Specifies the identifier key of the auditing storage account.
        /// 
        /// If state is Enabled and storageEndpoint is specified, not specifying the storageAccountAccessKey will use SQL server system-assigned managed identity to access the storage.
        /// 
        /// Prerequisites for using managed identity authentication:
        /// 
        /// 1. Assign SQL Server a system-assigned managed identity in Azure Active Directory (AAD).
        /// 
        /// 2. Grant SQL Server identity access to the storage account by adding &apos;Storage Blob Data Contributor&apos; RBAC role to the server identity.
        /// 
        /// For more information, see [Auditing to storage using Managed Identity authentication](https://go.microsoft.com/fwlink/?linkid=2114355).
        /// </summary>
        public string StorageAccountAccessKey { get; set; }
        /// <summary> Specifies the number of days to keep in the audit logs in the storage account. </summary>
        public int? RetentionDays { get; set; }
        /// <summary>
        /// Specifies the Actions-Groups and Actions to audit.
        /// 
        /// 
        /// 
        /// The recommended set of action groups to use is the following combination - this will audit all the queries and stored procedures executed against the database, as well as successful and failed logins:
        /// 
        /// 
        /// 
        /// BATCH_COMPLETED_GROUP,
        /// 
        /// SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP,
        /// 
        /// FAILED_DATABASE_AUTHENTICATION_GROUP.
        /// 
        /// 
        /// 
        /// This above combination is also the set that is configured by default when enabling auditing from the Azure portal.
        /// 
        /// 
        /// 
        /// The supported action groups to audit are (note: choose only specific groups that cover your auditing needs. Using unnecessary groups could lead to very large quantities of audit records):
        /// 
        /// 
        /// 
        /// APPLICATION_ROLE_CHANGE_PASSWORD_GROUP
        /// 
        /// BACKUP_RESTORE_GROUP
        /// 
        /// DATABASE_LOGOUT_GROUP
        /// 
        /// DATABASE_OBJECT_CHANGE_GROUP
        /// 
        /// DATABASE_OBJECT_OWNERSHIP_CHANGE_GROUP
        /// 
        /// DATABASE_OBJECT_PERMISSION_CHANGE_GROUP
        /// 
        /// DATABASE_OPERATION_GROUP
        /// 
        /// DATABASE_PERMISSION_CHANGE_GROUP
        /// 
        /// DATABASE_PRINCIPAL_CHANGE_GROUP
        /// 
        /// DATABASE_PRINCIPAL_IMPERSONATION_GROUP
        /// 
        /// DATABASE_ROLE_MEMBER_CHANGE_GROUP
        /// 
        /// FAILED_DATABASE_AUTHENTICATION_GROUP
        /// 
        /// SCHEMA_OBJECT_ACCESS_GROUP
        /// 
        /// SCHEMA_OBJECT_CHANGE_GROUP
        /// 
        /// SCHEMA_OBJECT_OWNERSHIP_CHANGE_GROUP
        /// 
        /// SCHEMA_OBJECT_PERMISSION_CHANGE_GROUP
        /// 
        /// SUCCESSFUL_DATABASE_AUTHENTICATION_GROUP
        /// 
        /// USER_CHANGE_PASSWORD_GROUP
        /// 
        /// BATCH_STARTED_GROUP
        /// 
        /// BATCH_COMPLETED_GROUP
        /// 
        /// 
        /// 
        /// These are groups that cover all sql statements and stored procedures executed against the database, and should not be used in combination with other groups as this will result in duplicate audit logs.
        /// 
        /// 
        /// 
        /// For more information, see [Database-Level Audit Action Groups](https://docs.microsoft.com/en-us/sql/relational-databases/security/auditing/sql-server-audit-action-groups-and-actions#database-level-audit-action-groups).
        /// 
        /// 
        /// 
        /// For Database auditing policy, specific Actions can also be specified (note that Actions cannot be specified for Server auditing policy). The supported actions to audit are:
        /// 
        /// SELECT
        /// 
        /// UPDATE
        /// 
        /// INSERT
        /// 
        /// DELETE
        /// 
        /// EXECUTE
        /// 
        /// RECEIVE
        /// 
        /// REFERENCES
        /// 
        /// 
        /// 
        /// The general form for defining an action to be audited is:
        /// 
        /// {action} ON {object} BY {principal}
        /// 
        /// 
        /// 
        /// Note that &lt;object&gt; in the above format can refer to an object like a table, view, or stored procedure, or an entire database or schema. For the latter cases, the forms DATABASE::{db_name} and SCHEMA::{schema_name} are used, respectively.
        /// 
        /// 
        /// 
        /// For example:
        /// 
        /// SELECT on dbo.myTable by public
        /// 
        /// SELECT on DATABASE::myDatabase by public
        /// 
        /// SELECT on SCHEMA::mySchema by public
        /// 
        /// 
        /// 
        /// For more information, see [Database-Level Audit Actions](https://docs.microsoft.com/en-us/sql/relational-databases/security/auditing/sql-server-audit-action-groups-and-actions#database-level-audit-actions).
        /// </summary>
        public IList<string> AuditActionsAndGroups { get; }
        /// <summary> Specifies the blob storage subscription Id. </summary>
        public Guid? StorageAccountSubscriptionId { get; set; }
        /// <summary> Specifies whether storageAccountAccessKey value is the storage&apos;s secondary key. </summary>
        public bool? IsStorageSecondaryKeyInUse { get; set; }
        /// <summary>
        /// Specifies whether audit events are sent to Azure Monitor.
        /// 
        /// In order to send the events to Azure Monitor, specify &apos;state&apos; as &apos;Enabled&apos; and &apos;isAzureMonitorTargetEnabled&apos; as true.
        /// 
        /// 
        /// 
        /// When using REST API to configure auditing, Diagnostic Settings with &apos;SQLSecurityAuditEvents&apos; diagnostic logs category on the database should be also created.
        /// 
        /// Note that for server level audit you should use the &apos;master&apos; database as {databaseName}.
        /// 
        /// 
        /// 
        /// Diagnostic Settings URI format:
        /// 
        /// PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Sql/servers/{serverName}/databases/{databaseName}/providers/microsoft.insights/diagnosticSettings/{settingsName}?api-version=2017-05-01-preview
        /// 
        /// 
        /// 
        /// For more information, see [Diagnostic Settings REST API](https://go.microsoft.com/fwlink/?linkid=2033207)
        /// 
        /// or [Diagnostic Settings PowerShell](https://go.microsoft.com/fwlink/?linkid=2033043)
        /// 
        /// .
        /// </summary>
        public bool? IsAzureMonitorTargetEnabled { get; set; }
        /// <summary>
        /// Specifies the amount of time in milliseconds that can elapse before audit actions are forced to be processed.
        /// 
        /// The default minimum value is 1000 (1 second). The maximum is 2,147,483,647.
        /// </summary>
        public int? QueueDelayMs { get; set; }
    }
}
