All information contained herein is considered proprietary and confidential. Any unauthorized disclosure or use is prohibited.
Background
To provide maximum flexibility and integration into existing systems, ACM utilizes a Microsoft SQL database to store device configurations, polling statistics, and collected EFM data.
Because SQL Server installations may be managed by an independent DBA teams tasked with minimizing security risks, it is necessary to describe the security permissions required for normal operation of ACM.
To Perform ACM Database Create/Updates:
The following instructions assume a DBA has created an empty database on the server, but the ACM user that will create the tables and objects in the database has not been created.
Create a login on the server level per corporate requirements (username, password, password policy etc)
On the “User Mapping” tab,
map the new login to the appropriate database and
make sure the schema is “dbo”.
Check the db_datareader, db_datawriter and public database roles in the “Database membership roles” box below the “Users Mapped”.
On the “Securables” tab:
with the server selected, select the “Grant” checkbox next to “View server state”
Click OK.
Refresh the “Security/Users” folder in the ACM database, right click the user you just created and choose “Properties”. Select the “Securables” tab.
Next add the other ACM database “Control” permission:
Click the “Search” button
Choose the “Specific Types” option,
Click OK,
Search for Object types “Database”
Click the “Browse” button
Select the ACM database you are working with
Click “OK”. The database will show up in the “Securables” grid.
With the database securable selected, check the “Grant” checkbox next to “Control”.
Minimum Permissions to run ACM (but not update the database schema)
The following instructions assume a DBA has created an empty database on the server, but the ACM user that will create the tables and objects in the database has not been created.
Create a login on the server level per corporate requirements (username, password, password policy etc)
On the “User Mapping” tab,
map the new login to the appropriate database and
make sure the schema is “dbo”.
Check the db_datareader, db_datawriter and public database roles in the “Database membership roles” box below the “Users Mapped”.
On the “Securables” tab:
with the server selected, select the “Grant” checkbox next to “View server state”
Click OK.