Unclear access
Accounts and permissions no longer match current roles. Identify owners, approved access, and the process for removing it.
Security baseline and access control setup
Establish the access rules, configuration, and operating checks your systems need. ACW reviews the current setup and implements an agreed security baseline with documented exceptions and responsibility for maintaining it.
Contact UsFind the gaps in everyday administration
Inconsistent settings
Environments use different configurations without a recorded reason. Decide which settings should follow a common baseline.
Missing operating checks
Teams cannot tell whether important controls remain enabled or who should investigate a change.
Define the baseline for the systems in scope
What your team receives
A baseline specifying systems, controls, and exceptions.
An account and permission review for the agreed scope.
Implemented configuration changes and verification records.
A list of unresolved gaps and required follow-up work.
Handover instructions and named maintenance responsibilities.
Implement changes without losing their context
- Step 01.
Review
Inventory the systems, accounts, existing controls, and operational constraints included in the engagement.
- Step 02.
Agree
Define intended settings, access requirements, exceptions, and how changes will be checked. Establish handling and retention of any evidence collected.
- Step 03.
Implement
Apply the approved changes in the agreed sequence. Identify changes needing a maintenance window or recovery plan.
- Step 04.
Verify and hand over
Check the resulting settings and relevant user flows. Record remaining gaps, who maintains the baseline, and what triggers a review.
Know what has been established
Acceptance should identify the settings and access rules changed, the checks performed, and any exceptions retained. Monitoring configuration does not establish a staffed response service; the person reviewing alerts and their coverage must be defined separately.
This is an example of a possible engagement, not an ACW client result.
Illustrative scope: administrative access
The team reviews administrator accounts, agrees who needs elevated access, and implements the selected authentication controls. Verification covers approved access and denied access. The handover records exceptions and who reviews account changes.
Questions before setup
Do we need a specific security tool?
Review the existing environment and required controls first. Product selection should follow identified gaps and operating capacity.
Can this cover one application?
Yes. Define its environments, accounts, integrations, and dependencies so the baseline has a clear boundary.
Does setup include ongoing monitoring?
Agree logging and alert configuration separately from ongoing review, response coverage, and maintenance responsibilities.
Establish the baseline your team can maintain
Tell us which systems need attention and how accounts, settings, and alerts are managed today.