Framework/Configurations/SVT/Services/AnalysisServices.json

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
{
    "FeatureName": "AnalysisServices",
    "Reference": "aka.ms/azsktcp/analysisservices",
    "IsMaintenanceMode": false,
  "Controls": [
    {
      "ControlID": "Azure_AnalysisServices_AuthZ_Grant_Min_RBAC_Access",
      "Description": "All users/identities must be granted minimum required permissions using Role Based Access Control (RBAC)",
      "Id": "AnalysisServices110",
      "ControlSeverity": "Medium",
      "Automated": "Yes",
      "MethodName": "CheckRBACAccess",
      "Rationale": "Granting minimum access by leveraging RBAC feature ensures that users are granted just enough permissions to perform their tasks. This minimizes exposure of the resources in case of user/service account compromise.",
      "Recommendation": "Remove any excessive privileges granted on the Analysis Service. Run command Remove-AzRoleAssignment -SignInName '{signInName}' -Scope '{scope}' -RoleDefinitionName '{role definition name}'. Run 'Get-Help Remove-AzRoleAssignment -full' for more help. Refer: https://docs.microsoft.com/en-us/sql/analysis-services/multidimensional-models/roles-and-permissions-analysis-services, https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-manage-users, https://docs.microsoft.com/en-us/azure/active-directory/role-based-access-control-manage-access-powershell",
      "Tags": [
        "SDL",
        "TCP",
        "Automated",
        "AuthZ",
        "RBAC",
        "AnalysisServices"
      ],
      "Enabled": true
    },
    {
      "ControlID": "Azure_AnalysisServices_AuthZ_Min_Admin",
      "Description": "Minimize the number of Analysis Service admins",
      "Id": "AnalysisServices120",
      "ControlSeverity": "Medium",
      "Automated": "Yes",
      "MethodName": "CheckAnalysisServicesAdmin",
      "Rationale": "Analysis Service admins have full access on the server to perform any operation. Each additional person in the admin role increases the attack surface for the server. The number of members in these roles should be kept to as low as possible.",
      "Recommendation": "Minimize the number of Analysis Service admins. Run command Set-AzAnalysisServicesServer -Name '{AnalysisServicesServerName}' -ResourceGroupName '{ResourceGroupName}' -Administrator '{Administrator}'. Refer: https://docs.microsoft.com/en-us/powershell/module/az.analysisservices/Set-AzAnalysisServicesServer",
      "Tags": [
        "SDL",
        "Best Practice",
        "Automated",
        "AuthZ",
        "AnalysisServices"
      ],
      "Enabled": true
    },
    {
      "ControlID": "Azure_AnalysisServices_AuthZ_Users_Min_DB_Permission",
      "Description": "Database users must be added to database roles with minimum required permission",
      "Id": "AnalysisServices130",
      "ControlSeverity": "Medium",
      "Automated": "No",
      "MethodName": "",
      "Recommendation": "Make sure that users are granted the least required privileges to databases and tabular models. Refer: https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-manage-users, https://docs.microsoft.com/en-us/sql/analysis-services/tabular-models/create-and-manage-roles-ssas-tabular",
      "Rationale": "Granting minimum access ensures that users are granted just enough permissions to perform their tasks. This minimizes permission of operations at the Analysis Server in case of user account compromise.",
      "Tags": [
        "SDL",
        "TCP",
        "Manual",
        "AuthZ",
        "AnalysisServices"
      ],
      "Enabled": true
    },
    {
      "ControlID": "Azure_AnalysisServices_AuthN_Analysis_Service_Clients",
      "Description": "Analysis Service clients should authenticate users using Azure Active Directory backed credentials",
      "Id": "AnalysisServices140",
      "ControlSeverity": "High",
      "Automated": "No",
      "MethodName": "",
      "Rationale": "Using the native enterprise directory for authentication ensures that there is a built-in high level of assurance in the user identity established for subsequent access control.All Enterprise subscriptions are automatically associated with their enterprise directory (xxx.onmicrosoft.com) and users in the native directory are trusted for authentication to enterprise subscriptions.",
      "Recommendation": "Analysis Services clients such as 'Power BI', 'Excel' or any BI Tools should authenticate users using Azure Active Directory backed credentials. Refer: (Power BI) https://docs.microsoft.com/en-us/azure/power-bi-embedded/power-bi-embedded-app-token-flow and (Excel) https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-connect-excel",
      "Tags": [
        "SDL",
        "Best Practice",
        "Manual",
        "AuthN",
        "AnalysisServices"
      ],
      "Enabled": true
    },
    {
      "ControlID": "Azure_AnalysisServices_DP_Encrypt_In_Transit",
      "Description": "Sensitive data must be encrypted in transit",
      "Id": "AnalysisServices150",
      "ControlSeverity": "High",
      "Automated": "No",
      "MethodName": "",
      "Rationale": "Use of HTTPS ensures server/service authentication and protects data in transit from network layer man-in-the-middle, eavesdropping, session-hijacking attacks.",
      "Recommendation": "Ensure that sensitive data is transmitted only on an encrypted channel through out the Analysis Service. Refer: https://blogs.msdn.microsoft.com/jason_howell/2013/02/26/how-do-i-ensure-analysis-services-client-tcp-connectivity-is-encrypted/",
      "Tags": [
        "SDL",
        "Information",
        "Manual",
        "DP",
        "AnalysisServices"
      ],
      "Enabled": true
    },
    {
      "ControlID": "Azure_AnalysisServices_DP_Encrypt_At_Rest",
      "Description": "Sensitive data must be encrypted at rest",
      "Id": "AnalysisServices160",
      "ControlSeverity": "High",
      "Automated": "No",
      "MethodName": "",
      "Rationale": "Using this feature ensures that sensitive data is stored encrypted at rest. This minimizes the risk of data loss from physical theft and also helps meet regulatory compliance requirements.",
      "Recommendation": "Default behavior. No action required.",
      "Tags": [
        "SDL",
        "Information",
        "Manual",
        "DP",
        "AnalysisServices"
      ],
      "Enabled": true
    },
    {
      "ControlID": "Azure_AnalysisServices_BCDR_Plan",
      "Description": "Backup and Disaster Recovery must be planned for Analysis Services",
      "Id": "AnalysisServices170",
      "ControlSeverity": "Medium",
      "Automated": "Yes",
      "MethodName": "CheckAnalysisServicesBCDRStatus",
      "Rationale": "Azure Analysis Service does not offer features to cover backup/disaster recovery out-of-the-box. As a result, when processing critical workloads, a team must have adequate backups of the data.",
      "Recommendation": "Go To Azure Portal => Analysis Services => Select Analysis Service => Go To Settings => Select Backups => Select Storage account details and enable backups, Refer: https://docs.microsoft.com/en-us/azure/analysis-services/analysis-services-backup",
      "Tags": [
        "SDL",
        "Best Practice",
        "Automated",
        "BCDR",
        "AnalysisServices"
      ],
      "Enabled": true
    }
  ]
}