Accelerynt Security Platform FAQs
Answers to common questions about Microsoft 365 security posture, configuration drift, compliance evidence, and how the platform works.
About the Platform Microsoft 365 Security Posture DevOps and Code Repository Security Compliance and Audit Attack Chains and Risk
About the Platform
Setup is guided. Your administrator connects a Microsoft 365 tenant by granting admin consent to the platform or by registering an app for it, and then runs the first scan. Every connection is read-only, and no agents are deployed to endpoints. Your first tenant typically connects in under ten minutes, and visibility starts the day your team signs in. GitHub connects through a GitHub App with read-only organization and repository permissions, and Azure DevOps uses the same platform credential with reader roles on the projects you choose. Azure subscriptions, AWS, GCP, and Google Workspace also connect with read-only access. A few Azure DevOps checks need Project Collection Administrator rights. Without them, those checks are marked as not performed and the rest of the assessment still completes.
Each customer runs in an isolated environment. Your findings sit in a database and key vault that belong to your environment alone, and no data store is shared between customers. The console Accelerynt uses to operate the service never stores your findings or credentials. When our team needs support access, the session is time limited and has to be started explicitly, and every action in it is recorded in an audit trail.
No. The Accelerynt Security Platform connects with read-only access and does not change configurations or run scripts in your tenant. Findings include remediation guidance, and some include scripts your team reviews and runs on its own terms.
Yes. Every tenant you manage appears in one console, with findings kept separate by tenant. Access is granted per tenant, so a team member can be limited to the tenants assigned to them. Azure DevOps and GitHub organizations, Azure subscriptions, and AWS and GCP accounts can be grouped under the Entra tenant they belong to. Companies that ended up with several tenants through growth or acquisition get the same single view, including tenants split between government and commercial clouds.
Yes. One console shows aggregated scores across Microsoft 365 and Entra ID along with Azure DevOps, GitHub, Azure subscriptions, AWS, GCP, and Google Workspace. Sort by worst first and open any score to see the findings behind it. The risk register lists every risk across those surfaces in one place, and your team can filter it by surface or by framework.
The platform includes a public API and signed webhooks, with ready-made delivery formats for Splunk, ServiceNow, Jira, PagerDuty, and Slack. Webhook events cover new and resolved findings, assigned remediation plans, the daily posture change, compliance and attack chain regressions, new critical exposures, and subdomain takeovers.
Yes. Findings come with remediation guidance that lists prerequisites and links to the relevant Microsoft Learn article, and some include scripts your team reviews and runs. Your team assigns each finding an owner and tracks it to a target date, with comments for anyone working on it, and each person sees their own assignments with reminders. Chain Breaker™ ranks the fixes that break the most attack chains, so your team knows which fix to make first.
Your team signs in through your existing identity provider using SAML or OIDC, and SCIM provisioning keeps each person’s access scoped to their role as people join, change roles, or leave. The platform has built-in roles for administrators, operators, auditors, and viewers, and administrators can build custom roles from individual permissions. Access can also be limited to specific tenants.
Scans run on a recurring schedule set for each tenant, and your team can also run a scan on demand. Between scans, a daily delta shows what changed in your posture over the last 24 hours, and drift detection compares critical controls with the baseline your team approved.
Microsoft 365 Security Posture
Configuration drift is when a security setting moves away from the state your team approved. An administrator edits a Conditional Access policy or grants a privileged role, and the tenant no longer matches its baseline. When several settings drift at once, they can open a path an attacker follows to reach higher-privilege accounts or sensitive data.
Yes. Drift detection compares your Conditional Access policies, privileged roles, PIM, Sentinel, and Defender settings with the baseline your team approved. You see each change with before and after values, when it happened, and the account responsible. Changes appear as in-app alerts, and the daily posture change can also go to your ticketing or chat tools by webhook.
Secure Score rates a tenant against Microsoft’s recommended actions. The Accelerynt Security Platform measures your tenant against the baseline your team approved and reads your Secure Score and its 30-day trend as one of its inputs. It adds external attack surface checks tied back to your tenant settings, drift monitoring for controls you have already fixed, attack chains that set the order of fixes, remediation scripts with an assignment workflow, one console across the tenants you manage, and framework reports an auditor will accept.
Control validation reads the administrative settings across Microsoft 365 and Entra ID, including Conditional Access, authentication methods, privileged roles and PIM, applications, Exchange, SharePoint, Teams, Intune, Defender, and Power Platform. The goal is to confirm each control works the way your team intended and to show where current settings create risk.
Yes. The platform reviews applications and service principals in Entra ID, including who owns each service principal, how credentials are managed, workload identity federation, and the permissions held by managed identities. It reviews app registrations for consent grants, risky permissions, and abandoned app identities, and it covers non-human identities, including authenticating agents, API connections, and agentic workflows. It also flags recent credential additions to service principals from the directory audit log. Each finding names the specific app or identity involved.
Yes. The platform checks your Copilot configuration and the SharePoint Advanced Management controls that limit Copilot oversharing, restricted access control and restricted content discovery. It shows oversharing, who has access, license usage, and what data Copilot and agents can reach, so your team knows which settings to change before a wider rollout.
A cloud security posture tool focuses on cloud infrastructure. The Accelerynt Security Platform checks the administrative layer of Microsoft 365 and Entra ID, and it also checks posture in Azure, AWS, GCP, Google Workspace, Azure DevOps, and GitHub. Findings map to the CIS foundations benchmark for each cloud, and attack chains connect gaps across those surfaces.
No. Sentinel and other SIEMs detect and respond to threats. The Accelerynt Security Platform checks how your environment is configured, including your Sentinel and Defender settings. While a finding is still open, it comes with a Sentinel detection rule your team can deploy to watch that gap until the fix lands. Findings can also be sent to Splunk and your other tools by webhook.
Yes. External scanning discovers your subdomains, open ports, exposed services, certificate problems, email and DNS security records, subdomains at risk of takeover, and exposed cloud storage. It also finds Entra tenants on your own domains that nobody is managing. Each external finding is tied back to the Entra ID and Microsoft 365 settings of the related tenant, and attack chains can start from an external finding and continue through internal gaps.
DevOps and Code Repository Security
Pipelines and code repositories hold the keys to your deployment infrastructure. A misconfigured service connection or an overprivileged personal access token can give an attacker a path from a code change to production access.
In Azure DevOps, the platform checks organization settings, branch protection, pipeline and agent pool security, service connections, personal access tokens, audit logging, and supply chain controls, with findings mapped to CIS DevOps Foundations and the MCSB DevOps Security controls. In GitHub, it checks organization membership and two-factor enforcement, repository visibility and branch protection, Actions workflows, secret scanning and Dependabot coverage, SSO enforcement, and audit log retention, with findings mapped to CIS GitHub Foundations.
Yes. A workflow that accepts a pull request from a fork and authenticates via OIDC with a permissive trust policy can allow an external contributor to escalate into your cloud environment without stealing a credential. The platform models this as an attack chain and identifies the specific trust-policy and workflow configurations that make it possible.
Compliance and Audit
Findings map across fifteen frameworks: NIST CSF 2.0, NIST 800-53, MITRE ATT&CK, CIS Microsoft 365, CISA SCuBA, Microsoft MCSB, HIPAA, PCI-DSS v4.0, ISO 27001:2022, CIS DevOps Foundations, CIS GitHub Foundations, CIS Azure Foundations, CIS AWS Foundations, CIS GCP Foundations, and CIS Google Workspace Foundations. Every finding carries its mappings, and findings export to CSV with all of them, so your compliance team can pull evidence by control without building a separate crosswalk.
Yes. Findings map to the CIS Microsoft 365 benchmark, and each finding names the specific policy or account behind the gap. The same findings also map to the other frameworks listed above.
Yes. Findings map to the CISA SCuBA baselines for Microsoft 365 and Google Workspace. For Microsoft 365, the platform also keeps a running SCuBA attestation. Each control’s configuration is fingerprinted so any tampering shows, an evidence bundle can be downloaded for your auditor, and your team is alerted when a SCuBA control moves from pass to fail. This reports alignment with the SCuBA baselines and is not a CISA certification. CISA’s Binding Operational Directive 25-01 requires federal civilian agencies to implement the mandatory SCuBA policies.
Those tools run useful checks, and if they are working for you, keep running them. The Accelerynt Security Platform turns those checks into a working program: a register that tracks findings over time, named ownership for fixes, change tracking, one view across your tenants, and evidence an auditor will accept. The checks start the job. The record after them is what the auditor asks to see.
Yes. Evidence comes from reading your live configuration, and every finding carries its framework mappings. Findings export to CSV with all mappings, framework reports export as HTML or PDF, and drift detection records each change with before and after values, when it happened, and the account responsible. The risk register keeps each finding’s history, owner, and remediation status, so the record is ready when the auditor asks.
Executives see aggregated scores for each area of the environment, sorted worst first, and any score opens to the findings behind it. The report builder lets your team choose the sections for a report, write the narrative around them, and export it as HTML or PDF for leadership. The risk register shows when each risk was found and where its remediation stands, and the daily delta shows what changed.
Attack Chains and Risk
An attack chain is a sequence of configuration gaps an attacker could follow from initial access to a high-value target. One Conditional Access gap may look minor on its own. Combined with an overprivileged service account and a missing MFA requirement, it becomes a path to lateral movement and privilege escalation. The platform maps these chains across every surface it checks, so your team can fix the gap that breaks the most of them.
Chain Breaker™ ranks remediations by how many active attack chains each one breaks, across every surface the platform checks. Your team works from the fixes that close the most paths first, and the What-If Simulator™ lets you remove any finding and see which attack chains break before you make the change. Attack chain results are saved with each assessment, so you can see the trend over time.
The breakout window is the time between an attacker’s initial access and their first move to other systems. Industry threat research put the average eCrime breakout time in 2025 at 29 minutes. That is the time your team has to detect and contain an intrusion before the attacker expands their access.
The platform includes regression alerting. When a configuration change or new finding opens an attack chain that was previously resolved, your team receives a notification. Your team sees when resolved risk reappears, rather than discovering it in the next scheduled review.

