Abakar Identity GroupManaged Identity and Access GovernanceBook a call
Abakar Identity Group
Managed Identity and Access Governance
Managed IAM · Entra ID · Okta · AWS IAM · Active Directory
Your identities are your #1 attack surface. We watch every one of them, every month.
Enterprise-grade identity governance for small and mid-sized businesses: access reviews, dormant account detection, privileged access analysis, and audit-ready compliance reports. Delivered monthly. No platform to buy, no agents to install, your identity data never touches a third-party cloud. Based in La Vista, Nebraska, we serve clients across the United States, remote first, so your team does not need to be in La Vista to work with us.
✓ Reviews Entra ID, Okta, AWS IAM, and Active Directory exports
✓ 10,000+ user environments
✓ Healthcare, financial services, and technology
✓ Based in La Vista, Nebraska · Serving clients across the United States, remote first
9+Years in IAM & cybersecurity
10k+Users governed across enterprises
6Organizations across healthcare, financial services, and technology
100%Local analysis with no third-party cloud exposure
Short answer
What does Abakar Identity Group do?
Abakar Identity Group provides Managed Identity and Access Governance for small and mid-sized businesses that use Microsoft Entra ID, Okta, AWS IAM, or Active Directory. For $497 to $1,997 per month, it provides monthly access reviews, dormant account detection, privileged access analysis, MFA coverage checks, and audit-ready compliance reports. AccessLens, the internal review tool behind the service, can review CSV exports from all four sources: Entra ID, Okta, AWS IAM, and Active Directory. AccessLens reviews a CSV export only. It has no live connection to Entra ID, Okta, AWS, or Active Directory, it does not manage any identity live, and it does not provision or remove access automatically. Analysis runs locally with a transparent rule-based risk model, so your identity data never goes to a third-party cloud, and you do not need to grant tenant admin access to start. The firm is based in La Vista, Nebraska and serves clients across the United States, remote first. Managed IAM, access reviews, and joiner mover leaver work are all delivered remotely, and clients do not need to be in La Vista.
Best for: Small and mid-sized businesses without a dedicated IAM specialist
Review sources: CSV exports from Microsoft Entra ID, Okta, AWS IAM, and Active Directory, plus any tabular access export shaped to the same format
Deliverables: Monthly compliance report, remediation plan, and manager review packets
Based in: La Vista, Nebraska, serving clients across the United States, remote first, with all work delivered remotely and no need to be in La Vista
The identity mess every SMB has (and won't admit)
Sound familiar? This is what auditors find, and what attackers exploit first.
Orphaned & dormant accounts
Ex-employees still enabled, service accounts nobody owns, guests from 2023. Every one is an unlocked door.
Standing privileged access
Global Admins who haven't signed in for months. Admin roles on accounts without MFA. The top audit finding and the top breach vector.
Audit panic
Compliance questionnaires, access reviews, and evidence requests eat weeks you do not have, and the paperwork is still stale when you submit it.
How the managed service works
Three steps. No agents, no console, no cloud connection to your tenant.
1
Export & send
Once a month, you export standard access reports from Entra ID, Okta, AWS IAM, or Active Directory (we provide detailed step by step instructions, and the demo below includes short export guides for AWS IAM and for Active Directory. The export takes about 10 minutes and can be completed by nontechnical staff).
2
Analysis runs locally and never in a third-party cloud
AccessLens reviews every identity in the export: sign-in activity, privileged roles, MFA coverage, ownership, license spend. It flags dormant accounts, excessive permissions, and orphaned access. AccessLens reviews the CSV export only, with no live connection to your systems, and it never provisions or removes access on its own. AccessLens is our internal analysis tool and it stays with Abakar Identity Group.
3
You get the deliverables
An audit-ready compliance report, a prioritized remediation plan with owners and target dates, access-review packets for your managers, and a walkthrough call to execute the fixes. You receive the service in your plan and the reports, findings, and remediation. You do not receive AccessLens itself, a login, or a copy of the tool.
How the analysis works: AccessLens is an internal tool used by Abakar Identity Group. Our analyst runs it locally and entirely offline to score every identity with a transparent and rule based risk model that considers dormant days, privilege level, MFA status, ownership, and account type, and to rank the findings for you. No cloud AI service ever sees your data, and every report shows exactly why any account was flagged. What you receive: AccessLens itself is not provided to customers, and customers do not get a login, a copy, or access to the tool. You receive the service in your plan and the reports, findings, and remediation that AccessLens produces.
What we manage for you
Eleven recurring services, run on a monthly cadence, so identity hygiene never slips back.
Direct answers
Common IAM questions, answered directly
Concise definitions and guidance on the identity topics small business owners and IT managers ask about most.
What is identity and access management (IAM)?
IAM is the set of policies and controls that decides who can sign in, what each person can access, and how that access is reviewed and removed. For a small business, IAM covers accounts in Microsoft Entra ID, Okta, AWS IAM, and Active Directory, admin roles, multifactor authentication, guest access, and employee offboarding.
What is a user access review?
A user access review is a scheduled check in which managers confirm that each person still needs the access they have. Reviewers approve, change, or revoke access for each account, and the recorded decisions become evidence for audits and compliance questionnaires.
What is privileged access?
Privileged access is any permission that can change systems, users, or security settings, such as a Global Administrator role. Standing privileged access means the permission is always active. The safer pattern is just-in-time elevation, where admin rights are granted only for the time they are needed.
What are dormant and orphaned accounts?
A dormant account is an enabled account that has not signed in for 90 days or more. An orphaned account is an account with no accountable owner. Both are high risk because they hold valid access that nobody monitors, and both are among the first things auditors and attackers look for.
What is MFA coverage, and why does it matter?
MFA coverage is the share of accounts that have a second sign-in factor registered. Accounts without MFA rely on a password alone, so a single stolen password is enough to sign in. Admin accounts without MFA are the highest priority gap to close.
How do access reviews help with SOC 2 and ISO 27001?
Auditors require evidence that access is reviewed on a regular schedule and that unneeded access is actually removed. Monthly review packets, decision logs, and remediation plans provide that evidence for SOC 2 criteria CC6.1 to CC6.3 and ISO 27001 controls A.5.15 to A.5.18.
Live demo
See a sample AccessLens report
This demo is a sample that shows what a client report looks like. It is not the tool customers receive. AccessLens is an internal tool used by Abakar Identity Group, and customers do not get a login, a copy, or access to AccessLens itself. AccessLens can review CSV exports from Entra ID, Okta, AWS IAM, and Active Directory. It reviews a CSV export only: it has no live connection to Entra ID, Okta, AWS, or Active Directory, it does not manage any identity live, and it does not provision or remove access automatically. The sample is loaded with a realistic dataset of 50 identities: dormant admins, ownerless service accounts, MFA gaps, and stale guests. No signup is required. Nothing is uploaded, and the demo runs entirely in your browser. It has eight sections, and every one works: Dashboard, Import Data, Findings, Access Reviews, JML Checklist, Compliance Report, Privacy & Compliance, and Settings. The JML Checklist section finds likely joiners, movers, and leavers in the data and builds a checklist for each person, with an approval record, a mark done control for every step, and a full audit trail that can be downloaded as a CSV file. The checklist never changes access itself: each step is carried out in the identity platform by a person, then marked done in AccessLens. On the Full JML plan, that person is a member of our service team. The Import Data section includes short export guides for AWS IAM and for Active Directory, showing how to shape an export to the ten columns AccessLens imports. You can also import your own CSV export and preview the report format here, locally. Work in AccessLens is saved automatically in your browser after each change and restored when the page is reopened, and the Delete all client data control in AccessLens and in Settings removes that saved work completely. As a customer, you receive the service in your plan and the reports, findings, and remediation that AccessLens produces.
AccessLensIdentity risk posture at a glanceSample data · 50 identities
Saved session restored
Saved session in this browser
AccessLens saves your work automatically in this browser after each change, so you can close and reopen this page and continue where you left off. Data stays on this device only. Nothing is uploaded, and AccessLens has no live connection to Entra ID, Okta, AWS, or Active Directory and does not provision or remove access automatically.
Delete all client data?
This permanently deletes the saved session in this browser. Export any reports and CSV logs you need to keep first, because this cannot be undone. The following will be deleted:
The saved session
Imported CSV data
Review decisions and reviewer assignments
Attestation decisions and reminder logs
JML approvals, completions, evidence, and audit logs
Settings, including branding and any logo image
Nothing has been deleted yet. The sample data will be shown again after deletion, with no client data saved. Tap Delete to delete everything listed above, or Cancel to keep it all.
0Identities analyzed
0Critical + high risk identities
0Dormant 90+ days (still enabled)
0Accounts without MFA
Risk in 3D
Four bars, one per risk band. Height is the number of identities. Drag to turn it, tap a bar for details.
The 3D view could not start on this device. The same data is shown in the risk breakdown and heatmap below.
Loading the 3D view…
Identity risk breakdown
Every identity scored from 0 to 100 by the local risk model.
Risk heatmap
Issue types across every application in the dataset.
Darker = more identities affected. Red = 8 or more.
Access Intelligence
Ask the engine about this dataset. Answers are computed locally from the loaded data. Try a question:
Findings
Prioritized identity risks with remediation guidance and the NIST SP 800-53 control for each finding. Identities are sorted by risk score, highest first. Select any row to see that identity’s findings, the NIST control behind each one, and the remediation to apply.
0Critical identities
0High identities
0Medium identities
0Low identities
0Total identities
Identity
Risk
Last sign-in
MFA
Privileged roles
Findings
Remediation guidance
Every finding in this dataset, in priority order, with the fix to apply for each one.
Import Data
Import a CSV export from Entra ID, Okta, AWS IAM, Active Directory, or any system that can export accounts. The file is parsed and analyzed in this browser only and it is never uploaded anywhere. The imported data is saved in this browser automatically, along with your decisions and settings, so it is still here when the page is reopened. Use the template for the exact column format, or reload the built-in sample data of 50 identities at any time. Imports are limited to CSV files up to 5 MB and 5,000 identity rows. After an import, the Dashboard, Findings, Access Reviews, and Compliance Report all update from your file.
Expected columns: name, email, type, department, applications, lastSignInDays, mfa, roles, owner, status. Applications and roles are separated with ;. Your file is parsed in this browser only and it is never uploaded anywhere. It is saved in this browser storage until you use Delete all client data.
Review only, by design: AccessLens reviews a CSV export. It does not manage any identity live, it does not provision or remove access automatically, and it has no live connection to Entra ID, Okta, AWS, or Active Directory. You export the data, AccessLens reviews the export, and every access change stays in your hands.
Export guides
Short guides for the two newest sources. Each one ends in the same ten columns AccessLens imports: name, email, type, department, applications, lastSignInDays, mfa, roles, owner, status.
AWS IAM export guide
Build the CSV from the IAM credential report plus the user and role lists. No AWS connection is needed by AccessLens at any point; you export, then import the file above.
Generate the credential report. In the AWS console, open IAM, then Credential report, then Generate report, then Download. It lists every IAM user with MFA status and last used dates for the console password and each access key.
List roles as well. In IAM, open Roles and note each role name, its attached policies, and its last activity date. Roles become rows too, with type set to Service.
Shape the ten columns in a spreadsheet, one row per user or role, using the mapping below.
Save as CSV and import the file above. Findings, Access Reviews, and the Compliance Report update from it.
Column mapping for AWS IAM
name: IAM user name or role name
email: the user contact email if you track one, otherwise leave blank
type: Employee for human users, Service for roles and service accounts
department: team or cost center, from tags if you use them
applications: AWS IAM, plus the AWS account name when you export more than one account
lastSignInDays: whole days since the password or access key last used date in the credential report; for roles, days since last activity
mfa: true when an MFA device is assigned to the user, otherwise false; roles are false
roles: attached policy names, separated with ; for example AdministratorAccess
owner: manager or team owner for the user or role
status: Enabled while the user or role is active, Disabled once its credentials are deactivated
Honest limit: AccessLens reviews this export only. It cannot sign in to AWS, read live IAM data, or change any user, role, or policy.
Active Directory export guide
Build the CSV with one PowerShell run on a machine with the Active Directory module, then shape two columns by hand. AccessLens never connects to your domain; you export, then import the file above.
Open PowerShell on a domain joined admin machine with the Active Directory module installed.
Run the export below. It writes one row per user with the name, email, department, applications set to Active Directory, last sign in in days, group based roles, manager, and account status in the AccessLens format.
Fill in the two columns AD does not store. Set type to Service for service accounts and Employee for people, and set mfa to true only for users enrolled in your MFA solution, otherwise false.
Save as CSV and import the file above. Findings, Access Reviews, and the Compliance Report update from it.
Column mapping for Active Directory
name: DisplayName
email: EmailAddress
type: Employee or Service, set by hand from the account purpose or its OU
department: Department
applications: Active Directory, plus any group driven applications, separated with ;
lastSignInDays: whole days since LastLogonDate; use 999 when the account has never signed in
mfa: true only when the user is enrolled in your MFA solution, otherwise false
roles: security group names from MemberOf, separated with ;
owner: manager name from the Manager property
status: Enabled or Disabled, from the Enabled property
Honest limit: AccessLens reviews this export only. It cannot query your domain live, and it cannot enable, disable, or change any account or group.
Access Reviews
Run a manager attestation here. Every identity is assigned to a reviewer, normally the manager or owner on record, and each reviewer works through their own attestation list with one click Approve or Revoke for every identity. Every decision is recorded with the reviewer name and a timestamp, and the full decision log can be downloaded as a CSV file for audit evidence. Flag for follow up is still available for anything that needs more checking first. Reviews are shown one page at a time, 25 or 50 per page, so even a 1,000 identity import stays fast to work through, and decisions are kept for the whole dataset as you move between pages.
0 of 0 reviewed
Attestation by reviewer
Completion rate and status for every reviewer, sorted so the reviewer with the most still outstanding appears first. That order is your chasing order. Use View list to open a reviewer attestation list, or generate the email draft for that reviewer from here.
Assign reviewers and choose a list
The reviewer starts as the owner on record for each identity. You can change the reviewer on any identity card below, assign every identity that has no reviewer in one step here, or reset all assignments back to the owner on record. An Approve or Revoke decision can only be recorded once a reviewer is assigned, because the audit log must name who decided.
Attestation emails and reminders
AccessLens is an internal offline tool, so it does not send email itself and it has no connection to your mail system. What it does is write the message for you. Choose a reviewer, generate the attestation request or the reminder, copy the draft, and send it from your own mail app. Every reminder you generate is counted in the reminder log above, so your chasing is recorded as well as your decisions.
Joiner Mover Leaver Checklist
AccessLens reads the imported data and flags the identities that look like joiners, movers, or leavers, then builds a checklist for each person. A joiner is flagged when a new account pattern appears, a mover when privileged access spans several applications in a way that suggests access kept from a previous role, and a leaver when an account is disabled, has been inactive for a long period, or is stale guest access. Every flag is a prompt to confirm with the manager or with HR records, not proof on its own. AccessLens does not provision or remove access automatically, and it has no live connection to Entra ID, Okta, AWS, or Active Directory. A person carries out each step in the identity platform, then marks the step done here. On the Full JML plan, that person is a member of the Abakar Identity Group service team. Record the approval first: who approved the change and when is stored with the case, every completed step stores who completed it and when, and the evidence field holds the ticket reference or note that proves the work was done. The full record downloads as a CSV file for audit evidence, and a summary of the checklist also appears in the Compliance Report.
0 of 0 checklist steps completed
JML audit trail
Every approval, evidence note, and completed step recorded in this section, in the order it happened, with the name of the person who recorded it and the time. This trail is the evidence that each joiner, mover, and leaver case was approved and carried out. Download the audit log above to keep it with the review records.
Execution stays in the identity platform: AccessLens prepares the checklist, the approval record, and the evidence trail only. It never creates an account, changes a role, or removes access in Entra ID, Okta, AWS, or Active Directory. Each step is done by a person in that platform, and marking a step done here records that the work was completed and who completed it.
Compliance Report
An audit ready summary of the current dataset: executive summary, top findings by risk score, a remediation plan with owners and target dates, a joiner mover leaver checklist section with case status, approval, and evidence for each detected case, a NIST SP 800-53 control mapping section, and a sign off block. The NIST section shows the framework behind each finding so the report can be handed to an auditor. It updates automatically whenever the data or the Settings change. This preview is a sample of the report a customer receives. AccessLens itself is not delivered to customers.
Privacy & Compliance
How this engine handles identity data, and how its output maps to the access-control evidence auditors ask for.
Analysis runs locally
AccessLens is an internal tool used by Abakar Identity Group and it runs locally. This demo is only a sample of the report format and it runs entirely in your browser: an imported CSV is parsed on your device, scored on your device, and never uploaded anywhere. Your imported data, decisions, assignments, attestation records, JML records, and settings are saved in this browser storage only, so the session is restored when the page is reopened. Closing the page does not delete that saved session. Use Delete all client data in AccessLens or in Settings to remove it completely, for example when a client asks for deletion or when the retention period ends. Customers do not receive AccessLens itself.
No tenant admin access needed
The service works from standard CSV exports that you generate yourself, from Entra ID, Okta, AWS IAM, or Active Directory. AccessLens has no live connection to any of those systems, it does not manage any identity live, and it does not provision or remove access automatically. No agents are installed, no cloud connector is attached to your tenant, and no third-party cloud service ever sees the raw identity data.
What customers receive
Customers do not get a login, a copy, or access to AccessLens. You receive the service in your plan and the reports, findings, and remediation that AccessLens produces. A signed Privacy & Data Handling Statement documents the approach and can be filed with your security review.
Transparent risk model
There is no cloud AI service involved. Every identity is scored with a rule-based model covering dormancy, privilege level, MFA status, ownership, and account type, and you can see the score and the specific reasons behind every flag. The thresholds can be adjusted in Settings.
How the output maps to audit frameworks
Abakar Identity Group is an evidence provider, not an auditor. These are the controls the deliverables support.
Deliverable
NIST SP 800-53
SOC 2
ISO 27001
Monthly access review with recorded manager decisions
AC-2 Account Management, AC-6 Least Privilege
CC6.1, CC6.3
A.5.15, A.5.17
Dormant and orphaned account findings with remediation
AC-2 Account Management
CC6.1, CC6.2
A.5.16, A.5.17
Privileged access certification
AC-6 Least Privilege
CC6.1, CC6.3
A.5.15, A.5.18
MFA coverage assessment
IA-2 Identification and Authentication (Organizational Users)
Disabled and guest access that still holds entitlements
AC-2 Account Management, AC-3 Access Enforcement
CC6.1, CC6.3
A.5.15, A.5.18
Joiner mover leaver checklist with approval record, step completion record, and audit trail
AC-2 Account Management, AC-6 Least Privilege
CC6.1, CC6.2, CC6.3
A.5.15, A.5.16, A.5.18
Compliance report with remediation plan, NIST control mapping, and sign off
AC-2, AC-6, IA-2, IA-5, AC-3
CC6.1 to CC6.3
A.5.15 to A.5.18
Every finding in the Compliance Report now carries its NIST SP 800-53 control beside the plain language remediation. For example, MFA findings map to IA-2, dormant and leaver access maps to AC-2, and privileged access maps to AC-6. The report includes a dedicated NIST section that groups findings by control, states what each control expects, and gives the recommended action for that control, so a client can hand the PDF or Word report to an auditor and show the framework behind the work.
Settings
Put your own branding on the reports you receive, and tune how the engine scores the current dataset. Applying the settings re-runs the analysis immediately, and the Dashboard, Findings, Access Reviews, and Compliance Report all update. Settings are saved in this browser automatically and restored when the page is reopened. Settings are never uploaded anywhere.
Branding
Your branding appears on the Compliance Report: the on-screen report, the preview in the Compliance Report section, and the PDF and Word downloads. Set it here, check the preview, then press Apply settings. Once applied, branding is saved in this browser along with the rest of the session and is never uploaded anywhere.
Brand color
Used for the report header band and the brand badge. Pick a color or tap a preset.
Logo image (optional)
Shown on the on-screen report and in the Word download, beside your organization name. PNG, JPEG, GIF, or WebP, up to 1 MB. The image is read in this browser only and it is never uploaded. Once applied, it is saved in this browser as part of your settings.
The preview updates as you type. Your reports and the demo header update when you press “Apply settings and re-analyze” below.
Scoring
These thresholds change how the engine scores the current dataset.
Saved session and client data
Your session is saved automatically in this browser after each change and restored when this page is reopened. The saved session is stored on this device only. It is never uploaded to a cloud service, and AccessLens has no live connection to Entra ID, Okta, AWS, or Active Directory and does not provision or remove access automatically.
Delete the saved session when a client asks for their data to be deleted or when the retention period for the work has ended. Export any reports and CSV logs you need to keep before you delete, because deletion cannot be undone from this page.
Imported CSV data
Review decisions and reviewer assignments
Attestation decisions and reminder logs
JML approvals, completions, evidence, and audit logs
Settings, including branding and any logo image
Delete all client data?
This permanently deletes the saved session in this browser. Export any reports and CSV logs you need to keep first, because this cannot be undone. The following will be deleted:
The saved session
Imported CSV data
Review decisions and reviewer assignments
Attestation decisions and reminder logs
JML approvals, completions, evidence, and audit logs
Settings, including branding and any logo image
Nothing has been deleted yet. The sample data will be shown again after deletion, with no client data saved. Tap Delete to delete everything listed above, or Cancel to keep it all.
Simple monthly pricing
No per-seat fees. No platform license. Cancel anytime. One client environment per subscription. Pricing covers the managed service in each tier and its deliverables. AccessLens is an internal tool used by Abakar Identity Group and is not included in any plan. Customers do not get a login, a copy, or access to AccessLens. You receive the reports, findings, and remediation for your tier.
Monitor
$497/mo
For lean IT teams who need the analysis and reports.
Monthly access review of Entra ID, Okta, AWS IAM, or Active Directory exports
Our service team runs the identity lifecycle for you, guided by the AccessLens JML Checklist.
Everything in Manage
Joiners, movers, and leavers found from your access export
A checklist built for each person, with approval and evidence recorded
Every step tracked to done, with a full audit trail and CSV export
Onboarding and offboarding carried out for you by our service team in your identity platform
Ticket handling for every joiner, mover, and leaver case
Vendor coordination for HR, device, and email changes
Quarterly roadmap review with leadership
AccessLens finds the cases and tracks the checklist. It does not provision or remove access automatically, and it has no live connection to your identity platform. Our service team makes each approved change in the platform itself, then marks the step done in AccessLens.
Annual commitment: no setup fee, plus a mid-year posture re-baseline. Monthly: $500 one-time onboarding. Every plan is a service delivered by Abakar Identity Group. AccessLens is not sold, licensed, or provided to customers in any tier.
About your analyst
Abakar Identity GroupManaged Identity and Access Governance
Hello, I am Abakar Ibn Oumar, founder of Abakar Identity Group. For nine years I have done exactly this work inside large enterprise environments: user access reviews and privileged access governance in a healthcare environment with more than 10,000 users, identity lifecycle automation in financial services, orphaned account reviews in global banking, and MFA deployment in a large technology and payments environment. I hold a Bachelor's Degree in Computer Information Systems from Bellevue University.
The tools enterprises use for this cost six figures a year. I built AccessLens to deliver the same discipline to businesses that cannot justify that cost, with a privacy first approach: your identity data never touches a third-party cloud. It goes only to your analyst, under our data handling agreement. AccessLens stays internal to Abakar Identity Group, so customers do not get a login, a copy, or access to the tool. Customers receive the service in their plan and the reports, findings, and remediation that AccessLens produces.
Abakar Identity Group is based in La Vista, Nebraska, which remains our home base, and we serve clients across the United States. The work is remote first by design. Managed IAM, access reviews, and joiner mover leaver support are delivered remotely through secure exports, review packets, and scheduled calls, so clients in any state receive the same service as clients in La Vista, and no one needs to be in La Vista to start.
Audit-ready evidenceRecurring access reviews reconciled across 3 identity systems in a large healthcare environment
Provisioning, deprovisioning & entitlementsEnterprise JML and entitlement administration in a major financial services environment
Orphaned accounts surfacedSplunk driven access review integration in a global banking environment
MFA deployed org-wideYubiKey and RSA rollout in a global payments environment
Frequently asked questions about managed IAM
Direct answers on cost, privacy, onboarding, and how the service works.
Do we need to be in La Vista to work with you?
No. Abakar Identity Group is based in La Vista, Nebraska and serves clients across the United States, remote first. Managed IAM, access reviews, and joiner mover leaver work are delivered remotely, using the exports, reports, and calls described on this page, so your location does not limit the service and you do not need to be in La Vista.
Do you need admin access to our tenant?
No. The core service needs only standard CSV exports that you generate yourself, and we provide exact instructions. For Full JML clients who want us to carry out changes, our service team works in your identity platform through an account that you create for a set period, with only the access the work needs, and that you can revoke at any time. AccessLens itself is not connected to your platform and never makes those changes.
How does our data stay private?
AccessLens is an internal tool used by Abakar Identity Group and it runs locally, never in a third party cloud. You send your standard export, an ordinary CSV, directly to your analyst by encrypted email or a secure link, handled under our data handling agreement, never to any cloud service or vendor platform. Customers do not receive AccessLens, a login, or a copy of the tool. You receive the reports, findings, and remediation produced from the analysis. A signed Privacy & Data Handling Statement documents the approach and can be filed with your security review.
Do we get AccessLens, a login, or a copy of the tool?
No. AccessLens is an internal tool used by Abakar Identity Group to perform the analysis. Customers do not get a login, a copy, or access to AccessLens itself. You receive the service in your plan and the reports, findings, and remediation that AccessLens produces. The demo on this site is only a sample that shows what a report looks like, not the tool customers receive.
How does the “AI-powered” analysis work if nothing goes to the cloud?
The engine scores every identity with a transparent, rule-based risk model based on dormant days, privilege level, MFA status, ownership, and account type, running entirely on a local machine. There is no cloud AI service involved at any point, which is exactly why your data stays private. You can see the score and the specific reasons behind every flag, in the demo above and in every client report.
We already have an IT provider or MSP. Does this conflict?
No. We are additive. MSPs rarely specialize in identity governance. We handle the access review and compliance layer and coordinate with your MSP for the fixes.
Can you review AWS IAM and Active Directory as well as Entra ID and Okta?
Yes. AccessLens can review CSV exports from Entra ID, Okta, AWS IAM, and Active Directory, all in the same ten column format: name, email, type, department, applications, lastSignInDays, mfa, roles, owner, and status. The Import Data section of the demo above includes a short export guide for AWS IAM and a short export guide for Active Directory. AccessLens also accepts any other tabular access export that can be shaped into those ten columns.
Does AccessLens connect live to Entra ID, Okta, AWS, or Active Directory?
No. AccessLens reviews a CSV export only. It has no live connection to Entra ID, Okta, AWS, or Active Directory, it does not manage any identity live, and it does not provision or remove access automatically. You export the data, AccessLens reviews the export, and any change to access is made by a person in the identity platform, never by AccessLens. On the Full JML plan, our service team makes the approved changes, guided by the JML Checklist.
How does the joiner mover leaver checklist in AccessLens work?
AccessLens reads the CSV export and flags the identities that look like joiners, movers, or leavers, then builds a five step checklist for each person. The checklist records who approved the change and when, holds an evidence note for the work, and has a mark done control for every step that records who completed the step and when. AccessLens does not provision or remove access automatically and it has no live connection to any identity platform. Each step is carried out in the identity platform by a person, then marked done in AccessLens. On the Full JML plan, our service team carries out the onboarding and offboarding steps for you. On other plans, the reviewer or your IT person carries them out. The full checklist and its audit trail download as CSV files, and a summary appears in the compliance report, so the approval and completion record can be filed as audit evidence.
Does AccessLens save the work, and how is client data deleted?
Yes. AccessLens saves the session in the browser on the device where the work is done, after each change, and restores it when the page is reopened. The saved session covers the imported data, review decisions, reviewer assignments, attestation decisions and reminder logs, JML approvals, completions and evidence, and settings. The data stays local only: it is never uploaded to a cloud service, and AccessLens has no live connection to Entra ID, Okta, AWS, or Active Directory. The Delete all client data control in AccessLens and in Settings wipes the saved session, the imported data, all decisions and logs, and the settings from that browser, after a confirmation, so data can be removed when a client asks for deletion or when the retention period ends.
What does the Full JML plan include?
Full JML costs $1,997 per month and includes everything in Manage. AccessLens finds joiners, movers, and leavers from your access export, builds a checklist for each person with approval and evidence recorded, and tracks every step to done, with a full audit trail and CSV export. AccessLens does not provision or remove access automatically, and it has no live connection to your identity platform. Onboarding and offboarding are carried out by the Abakar Identity Group service team, in your identity platform, using the checklist. The plan also includes ticket handling for every case, vendor coordination for HR, device, and email changes, and a quarterly roadmap review with leadership. AccessLens stays internal to Abakar Identity Group, and customers receive the service and its reports, not the tool.
Can you help us pass SOC 2 or ISO 27001?
The deliverables map directly to the access review and access control evidence those audits expect, including SOC 2 criteria CC6.1 to CC6.3 and ISO 27001 controls A.5.15 to A.5.18. We are evidence providers, not auditors. Your auditor will get what they need.
What does onboarding look like?
Week 1 covers a baseline export, threshold configuration, and the first analysis. Week 2 covers the report walkthrough and a 30-day remediation plan. Week 4 delivers the first review packets to managers. You are fully operational within a month.
What is managed IAM?
Managed IAM is an outsourced service that handles identity governance for you on a recurring schedule. It includes access reviews, dormant account detection, privileged access checks, MFA coverage checks, and compliance reporting. Abakar Identity Group provides managed IAM monthly, reviewing CSV exports from Microsoft Entra ID, Okta, AWS IAM, and Active Directory environments.
How much does managed IAM cost for a small business?
At Abakar Identity Group, managed IAM costs $497 per month for the Monitor plan, $997 per month for the Manage plan, and $1,997 per month for the Full JML plan. There are no per-seat fees and no platform license to buy. Full details are in the Pricing section on this page.
How often should a business run user access reviews?
Most small and mid-sized businesses should run user access reviews monthly and privileged access reviews quarterly. Monthly reviews catch dormant accounts and leftover access soon after people change roles or leave. Quarterly certification gives every admin role a documented owner decision.
What is a dormant account?
A dormant account is an enabled user, service, or guest account that has not signed in for an extended period, typically 90 days or more. Dormant accounts are risky because they hold valid access that nobody monitors. The standard fix is to disable the account, confirm ownership, and remove access that is no longer needed.
What is the difference between disabling and deprovisioning an account?
Disabling an account blocks sign-in but leaves its roles, group memberships, and application access in place. Deprovisioning removes those entitlements as well. An account is only fully offboarded when it has been deprovisioned, because a disabled account can be reactivated later with all of its old access intact.
Let's see what your identity risk actually looks like
Send me a note and we'll book a 20-minute intro call. Or run the live demo first and bring your questions. The email button below includes the details I need to reply usefully.
If “Open in your mail app” does nothing, your phone may not have a mail account set up, or the app you are viewing this page in may block mail links. That is the usual reason a mail link appears dead. The message preview below then opens with the full message selected, ready to copy, or use “Compose in Gmail” instead.