Search
Intermediate Certificate on pass

Security Settings Admin

IP allowlist, MFA policy, retention, and device rules.

3 lessons 40 min 5-question assessment 70% to pass

What you’ll learn

  • Explain the security and compliance control purpose behind security settings admin
  • Configure policy settings, rules, and user roles to enforce least privilege
  • Handle security events, user support, recovery, and audit investigations
  • Provide audit-ready evidence and documentation for compliance verification

Course content

3 lessons · 40 min of reading
01
Lesson 1 of 3 Reading 12 min

Set IP boundaries

Security Settings Admin focuses on configuring global security settings, IP allowlists, tenant-wide MFA, and device compliance rules. In AWRA, security and compliance are built into every level: from authentication and permissions to log files and recovery mechanisms.

The main objective is risk control. System owners and security teams should know how to prevent drift, recover from incidents, and verify that actual access matches policy definitions.

In practice, a tenant administrator updates the IP allowlist, restricts login hours, sets device trust policies, and configures retention parameters.

Security configuration path

1

Evaluate

Identify required IP boundaries, MFA rules, and device requirements.

2

Update

Configure rules in the global security settings console.

3

Test

Verify that access is restricted without blocking valid users.

4

Publish

Apply settings and monitor access logs for exceptions.

Control model

  • Access and recovery rules should always reflect policy agreements.
  • Least privilege is a habit, not a one-time project.
  • Incident response needs clear ownership and evidence capture.
  • Unusual signals should trigger immediate review and investigation.
02
Lesson 2 of 3 Workshop 14 min

Enforce session rules

The operating routine is to configure IP allowlists, set MFA enforcement rules, define device compliance, and update settings locks. That sequence prevents errors and keeps security practices aligned with organizational guidelines.

Before taking action, check allowed IP addresses, MFA exception groups, device OS version limits, and settings change approvals. These checkpoints protect users, roles, devices, data privacy, and the integrity of operations.

A secure administrator can identify the appropriate response directly from the system logs, user context, or control panels.

Security config guide

Signal Check Action
New office IP Verify network security credentials Add IP to tenant allowlist
MFA policy update Review user impact timeline Enable enforcement with 7-day grace
Outdated device rule Evaluate OS compatibility Set minimum OS version requirement
Settings lock triggered Check administrator approvals Validate settings updates

Response decisions

  • Route critical changes through approvals and audit steps.
  • Review access logs and device lists on a clear cadence.
  • Ensure recovery options remain up-to-date and tested.
  • Keep policies simple and easy for the team to follow.
03
Lesson 3 of 3 Practice 14 min

Lock security policies

Security and recovery actions should leave proof. Useful evidence includes security configuration files, IP allowlist logs, settings approval notes, and system policy updates, which is essential for audits, incident reviews, and regulatory checks.

Management should review trends rather than isolated events: recurring lockouts, permission drift alerts, unusual logins, or missing audit records usually point to systemic risks.

In practice, closure means security configurations are active, tested, and locked against unauthorized edits, logging all policy updates.

Security admin checklist

IP allowlist is updated
MFA enforcement is configured
Device rules are active
Policy settings are locked
Change logs record the updates

Compliance proof

  • Proof of compliance should be stored securely and be easily retrievable.
  • Incidents are not resolved until corrective actions and evidence are documented.
  • Regular audit log reviews are the primary control against undetected drift.
  • Recovery procedures should be verified to confirm they restore full integrity.

Finished the material?

Take the 5-question assessment and earn your certificate — 70% to pass.

Take the assessment

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center