<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>rbac &#8211; Blue Lance</title>
	<atom:link href="https://bluelance.com/docs-tag/rbac/feed/" rel="self" type="application/rss+xml" />
	<link>https://bluelance.com</link>
	<description></description>
	<lastBuildDate>Tue, 02 Jun 2026 23:10:53 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.0</generator>

<image>
	<url>https://bluelance.com/wp-content/uploads/2025/11/fevicon-ic-1.png</url>
	<title>rbac &#8211; Blue Lance</title>
	<link>https://bluelance.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Configuring Reporting Console Database Access</title>
		<link>https://bluelance.com/docs/configuring-reporting-console-database-access/</link>
		
		<dc:creator><![CDATA[peter thomas]]></dc:creator>
		<pubDate>Thu, 28 May 2026 16:18:27 +0000</pubDate>
				<guid isPermaLink="false">https://bluelance.com/?post_type=docs&#038;p=15845</guid>

					<description><![CDATA[Access to the LT Auditor MP Reporting Console is controlled through a combination of a SQL Server database role and an Active Directory security group. This approach centralizes access management and ensures only authorized users can run reports from the console. Prerequisites: Before beginning, confirm you have: Step 1 — Create an Active Directory security [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Access to the LT Auditor <sup>MP</sup> Reporting Console is controlled through a combination of a SQL Server database role and an Active Directory security group. This approach centralizes access management and ensures only authorized users can run reports from the console.</p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p class="wp-block-paragraph"><strong>Prerequisites:</strong></p>



<p class="wp-block-paragraph">Before beginning, confirm you have:</p>



<ul class="wp-block-list">
<li>SQL Server access with administrative privileges</li>



<li>Active Directory access to create and manage security groups</li>



<li>Access to the LT Auditor <sup>MP</sup> production database (LTAProductionDB)</li>
</ul>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p class="wp-block-paragraph"><strong>Step 1 — Create an Active Directory security group:</strong></p>



<ol class="wp-block-list">
<li>Open <strong>Active Directory Users and Computers</strong></li>



<li>Create a new security group (e.g., LT Auditor Report Users)</li>



<li>Add all users who require access to the Reporting Console to this group</li>
</ol>



<p class="wp-block-paragraph"><em>[Your administrator should confirm the naming convention and OU location for new security groups in your environment.]</em></p>



<hr class="wp-block-separator has-alpha-channel-opacity"/>



<p class="wp-block-paragraph"><strong>Step 2 — Create the SQL Server role and assign permissions:</strong></p>



<p class="wp-block-paragraph">Run the following SQL script against the LTAProductionDB database. This script creates the ReportUsers role and grants it the necessary execute permissions on stored procedures and select permissions on views required by the Reporting Console.</p>



<pre class="wp-block-code"><code>\-- ============================================================
-- Create Role
-- ============================================================
IF NOT EXISTS (SELECT 1 FROM sys.database_principals WHERE name = 'ReportUsers')
BEGIN
    CREATE ROLE ReportUsers;
END
GO

-- ============================================================
-- Grant EXECUTE on Stored Procedures
-- ============================================================
GRANT EXECUTE ON OBJECT::dbo.usysr_RptUserSAll TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usys_LkpConsS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usys_LkpConsSelectByAuditSS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usys_LkpConsSelectByAuSS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usys_LkpConsSelectByOperation TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usys_LkpConsSelectSelected TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usys_LKPOPsS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usys_LkpOpsSByAuSS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usys_LkpOpsSForCPAAuSS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usys_LkpOpsSSed TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysc_AuditSubsystemsS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysc_AuditSubsystemsSAll TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysc_AuditSubsystemsSWin TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysc_AuditSubsystemsKeyU TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptCatsD TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptCatsI TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptCatsS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptCatsSByAuSS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptCatsSByParent TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptCatsU TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RPTEmailCCD TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RPTEmailCCI TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RPTEmailCCS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RPTEmailCCSByQueryID TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RPTEmailCCU TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RPTEmailToD TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RPTEmailToI TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RPTEmailToS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RPTEmailToSByQueryID TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RPTEmailToU TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptEntitiesD TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptEntitiesDByList TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptEntitiesI TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptEntitiesS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptEntitiesU TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptEntityListCollS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptEntityListD TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptEntityListI TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptEntityListS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptEntityListU TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptEntityMembersS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptFilesD TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptFilesI TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptFilesS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RPTFilesSByAuSS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptFilesU TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptOpsD TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptOpsI TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptOpsS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptQueriesD TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptQueriesI TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptQueriesS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptQueriesU TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptQueryCollectionsS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RPTSelOpsS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptSMTPD TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptSMTPI TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptSMTPS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptSMTPU TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptStatementsByQueryS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptStatementsD TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptStatementsI TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptStatementsS TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usysr_RptStatementsU TO ReportUsers;
GRANT EXECUTE ON OBJECT::dbo.usys_BLDBVersionS TO ReportUsers;

-- ============================================================
-- Grant SELECT on Views
-- ============================================================
GRANT SELECT ON OBJECT::dbo.VIEW_ADA_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_ATA_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_EFS_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_FSA_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_LSA_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_RSM_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_TEMPXPA_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_XPA_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_CPA_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_GPA_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_LTA_REPORT_80 TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_NEL_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_NWA_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_RDA_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_TEMPAA8_DATA TO ReportUsers;
GRANT SELECT ON OBJECT::dbo.VIEW_AA8_DATA TO ReportUsers;</code></pre>



<p class="wp-block-paragraph"><strong>Step 3 — Map the Active Directory group to the SQL role:</strong></p>



<p class="wp-block-paragraph">After running the script, map your AD group to the ReportUsers role by running the following command, replacing DOMAIN\GroupName with your actual domain and group name:</p>



<pre class="wp-block-code"><code>ALTER ROLE ReportUsers ADD MEMBER &#91;DOMAIN\GroupName];</code></pre>



<p class="wp-block-paragraph"><strong>Step 4 — Validate access:</strong></p>



<ol class="wp-block-list">
<li>Log in as a user who is a member of the AD group</li>



<li>Open the LT Auditor <sup>MP</sup> Reporting Console</li>



<li>Confirm the user can successfully access and run reports</li>



<li>If access is denied, verify:
<ul class="wp-block-list">
<li>The user is a member of the correct AD group</li>



<li>The AD group has been correctly mapped to the ReportUsers SQL role</li>



<li>The SQL script completed without errors</li>
</ul>
</li>
</ol>



<p class="wp-block-paragraph"><em>[Your administrator should confirm the correct domain and group name before running the mapping command, and retain a record of which AD group is mapped to the ReportUsers role for future reference.]</em></p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Access Web Portal</title>
		<link>https://bluelance.com/docs/initial-configuration-checklist/</link>
		
		<dc:creator><![CDATA[peter thomas]]></dc:creator>
		<pubDate>Thu, 28 May 2026 16:18:18 +0000</pubDate>
				<guid isPermaLink="false">https://bluelance.com/?post_type=docs&#038;p=15837</guid>

					<description><![CDATA[After completing installation and verifying that all services are running, complete the following steps before going live. This checklist ensures LT Auditor MP is properly configured to collect data, send alerts, and support your team&#8217;s day-to-day operations. 1. Change the default admin password Log in to the Web UI and immediately change the default administrator [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">After completing installation and verifying that all services are running, complete the following steps before going live. This checklist ensures LT Auditor <sup>MP</sup> is properly configured to collect data, send alerts, and support your team&#8217;s day-to-day operations.</p>



<p class="wp-block-paragraph"><strong>1. Change the default admin password</strong> Log in to the Web UI and immediately change the default administrator password to a strong, unique password.</p>



<ol class="wp-block-list">
<li>Navigate to <strong>Admin → User Management</strong></li>



<li>Select the admin account</li>



<li>Click <strong>Change Password</strong></li>



<li>Enter and confirm a new password</li>



<li>Click <strong>Save</strong></li>
</ol>



<p class="wp-block-paragraph"><strong>2. Configure SMTP for email alerts</strong> Set up email delivery so that alerts and scheduled reports can be sent to your team.</p>



<ol class="wp-block-list">
<li>Navigate to <strong>Admin → SMTP Settings</strong></li>



<li>Enter your mail server details:
<ul class="wp-block-list">
<li><strong>SMTP Host</strong></li>



<li><strong>Port</strong></li>



<li><strong>Authentication credentials</strong></li>



<li><strong>From address</strong></li>
</ul>
</li>



<li>Send a test email to confirm delivery</li>



<li>Click <strong>Save</strong></li>
</ol>



<p class="wp-block-paragraph"><em>[Your administrator should fill in the specific SMTP server details for your environment.]</em></p>



<p class="wp-block-paragraph"><strong>3. Install and connect modules</strong> Install the relevant modules for your environment and confirm they are sending data to the LT Auditor <sup>MP</sup> server. Refer to each module&#8217;s dedicated documentation section for full instructions.</p>



<figure class="wp-block-table"><table class="has-fixed-layout"><tbody><tr><td><strong>Module</strong></td><td><strong>Data Source</strong></td></tr><tr><td>EventLogCentral</td><td>Windows Event Logs &amp; NTFS file activity</td></tr><tr><td>PowerShell Orchestrator</td><td>Active Directory &amp; Entra ID assessments</td></tr><tr><td>PII Scanner</td><td>Sensitive data on Windows &amp; Linux systems</td></tr><tr><td>EntraConnector</td><td>Azure sign-in &amp; Entra ID audit logs</td></tr><tr><td>NSS Module</td><td>OES NSS file activity</td></tr></tbody></table></figure>



<p class="wp-block-paragraph"><strong>4. Configure monitored scopes</strong> Define which servers, directories, and systems LT Auditor <sup>MP</sup> should monitor.</p>



<ol class="wp-block-list">
<li>Navigate to <strong>Configure → Environments</strong></li>



<li>Add each environment relevant to your deployment (Windows, Linux, eDirectory, etc.)</li>



<li>Define log categories and operations to capture within each environment</li>



<li>Save your configuration</li>
</ol>



<p class="wp-block-paragraph"><strong>5. Set up alert rules</strong> Configure at minimum a basic set of alert rules to notify your team of critical events. See the Configuring Alert Rules article for full instructions.</p>



<p class="wp-block-paragraph">Recommended starting alerts:</p>



<ul class="wp-block-list">
<li>Failed login threshold exceeded</li>



<li>Privileged account changes</li>



<li>File deletion on sensitive directories</li>



<li>New admin account created</li>
</ul>



<p class="wp-block-paragraph"><strong>6. Configure data retention policy</strong> Set how long audit data is retained in the database to manage storage and meet compliance requirements.</p>



<ol class="wp-block-list">
<li>Navigate to <strong>Admin → Retention Settings</strong></li>



<li>Set the retention period in days</li>



<li>Click <strong>Save</strong></li>
</ol>



<p class="wp-block-paragraph"><strong>7. Set up user roles and access</strong> Create user accounts and assign appropriate roles for your team before sharing access to the platform.</p>



<ol class="wp-block-list">
<li>Navigate to <strong>Admin → User Management</strong></li>



<li>Add user accounts for each team member</li>



<li>Assign roles based on responsibilities (admin, analyst, report viewer, etc.)</li>



<li>Save all changes</li>
</ol>



<p class="wp-block-paragraph"><strong>8. Test an alert end-to-end</strong> Before going live, confirm that the full alert pipeline is working correctly.</p>



<ol class="wp-block-list">
<li>Trigger a test event that matches one of your alert rules</li>



<li>Confirm the alert appears in <strong>Alerts → Active Alerts</strong></li>



<li>Confirm the alert notification email is received</li>



<li>Resolve the test alert</li>
</ol>



<p class="wp-block-paragraph"></p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
