Planning SAP GRC or Pathlock? Start With MTC Skopos.

Planning SAP GRC or Pathlock? Start with MTC Skopos.

MTC Skopos before SAP GRC: if you are planning an SAP GRC or Pathlock implementation, run SoD analysis and remediation with MTC Skopos first. Clean your roles before automating provisioning, keep them clean during rollout, and transfer your validated ruleset to your GRC platform at go-live, so none of the work is lost.

If your organization has decided to implement SAP GRC Access Control or Pathlock for integrated provisioning, access requests and emergency access on your core systems, the open question is what happens between now and go-live. Your segregation of duties risks are not on hold while your GRC platform gets configured.

SAP GRC implementations take months. Sometimes over a year. Pathlock rollouts are no different when you consider the full scope: configuring rulesets, designing workflows, integrating with your identity provider, onboarding business process owners, testing, fixing, testing again. It is a serious project.

Meanwhile, auditors still want a clean access matrix. New roles still get created. Provisioning decisions still need some visibility into the risks they create, and MTC Skopos can provide it during the project.

How to measure your SoD risk before a GRC project

Most GRC business cases are written before anyone knows the real conflict count, which is how implementations get sized on estimates. Running an analysis first fixes that: install MTC Skopos on a laptop, point it at an SAP RFC connection or a CSV export of your roles and users, and get the actual numbers the same day. Skopos analyzes both role-level and user-level conflicts at the authorization-object level, produces a ranked remediation report, and lets you simulate role changes before they go live.

If you are not planning a GRC project at all and simply want the detection without the suite, that path is covered on the SoD analysis without GRC or production access page.

The steps are short:

  1. Connect or import. Connect to SAP via RFC, or load a CSV export of role and user data for systems where direct connection is not available.
  2. Load a ruleset. Skopos ships with a template SoD ruleset for SAP transactions and authorization objects, a starting point you review and tune to your own processes. You can also import an existing rule book if you have one, or build your own.
  3. Run the analysis. Role-level conflicts identify risks built into role design itself. User-level conflicts surface combinations that arise from multiple role assignments.
  4. Review the remediation report. Each finding is ranked by business impact and includes the specific authorization values that need to be split.
  5. Simulate before applying. Test proposed role and user changes against the ruleset before deployment, so fixing one conflict does not introduce another.

This is the fastest way to get audit-ready SoD coverage where there is no GRC. Organizations use the same approach to clean up before they implement SAP GRC or Pathlock, and the work transfers, as the rest of this article explains.

SoD analysis and remediation before GRC go-live

A common mistake with GRC implementations is going live on top of messy roles. If you automate provisioning before cleaning them up, the GRC workflow distributes risky access faster than before.

There is no implementation project. You install it, point it at your SAP data, and run a full SoD and critical access analysis on your current role design. The analysis covers role-level, user-level and cross-system conflicts, and you can start remediating the same day.

Arriving at SAP GRC go-live with clean roles also means fewer emergency fixes after go-live.

Stay clean during rollout

Role remediation is not a one-time event. Between the day you clean up your roles and the day your GRC platform goes live, people still need access, roles still get modified, and business does not stop.

During that period you can simulate role assignments in Skopos before they happen. When a manager requests a new role for a user, you run the simulation, check the SoD conflicts and decide. It isn't the automated workflow you are building, but it gives you risk visibility on each provisioning decision until that workflow is ready.

Without this, months of remediation work can quietly unravel before your GRC suite even goes live.

Your SoD ruleset transfers directly

One concern we hear from organizations planning a GRC rollout: if we build a ruleset in Skopos now, do we lose that work when SAP GRC or Pathlock goes live?

No. The SoD ruleset you build in Skopos converts to SAP GRC or Pathlock format, so the work carries over.

Ruleset quality is often the hardest part of a GRC rollout, harder than the technology. Getting business process owners to agree on what counts as a conflict, tuning out false positives and matching the rules to how your organization operates all take iteration. Skopos lets you iterate quickly, with immediate feedback, without spinning up a full GRC environment. By the time your platform goes live, your ruleset has already been through real data and real discussions with process owners.

How MTC Skopos and SAP GRC complement each other

SAP GRC Access Control and Pathlock are workflow platforms. They automate provisioning, manage periodic reviews, handle firefighter sessions, and orchestrate access requests across connected systems.

MTC Skopos is a SoD risk analysis and remediation tool. It runs analysis across any system, produces remediation paths, and works without infrastructure. You install it, point it at data, and get answers. If you want to understand how it compares to other tools in the space, see our SoD tools comparison.

The two complement each other: the analysis tells you what to clean, and the workflow platform keeps it clean once connected.

What happens after GRC go-live

In practice, SAP GRC or Pathlock goes live on the core systems: the main S/4HANA system and maybe a few satellite instances. Provisioning is automated, workflows are in place, audit is satisfied.

Then the scope question comes up.

The regional SAP instance that was not in the GRC project plan. The legacy ECC system that is being decommissioned "next year," for the third year in a row. The non-SAP ERP that finance quietly relies on. The warehouse management system no one remembered to include.

Extending your GRC suite to every system has a cost and a timeline, and the audit team still expects SoD coverage on the systems your workflow platform doesn't reach.

Skopos already has your tuned ruleset and already runs on those systems, so most organizations keep it for the systems that don't justify a full platform connector.

How this looks in practice

If you are planning an SAP GRC or Pathlock implementation, this is the sequence that works:

  1. Run Skopos against your current systems, see your SoD risks and start remediating, without a project plan or infrastructure. You can start with a quick risk assessment to see where you stand.

  2. Build and validate your ruleset. Iterate on your risk definitions with business process owners. Get your ruleset right before loading it into your GRC platform.

  3. Keep running Skopos during the implementation. Use it for day-to-day risk checks on provisioning decisions while your GRC workflows are being configured and tested.

  4. Convert your SoD ruleset at go-live. Your target platform starts with a proven, refined rule set instead of a theoretical one.

  5. Keep Skopos for the rest. After go-live, use it for every system your GRC suite does not cover.

Each step feeds into the next, and the work you do in Skopos becomes the starting point for your GRC platform.

Contact us to see how Skopos fits into your GRC roadmap.

Frequently asked questions

Can MTC Skopos replace SAP GRC Access Control?

They serve different purposes and work well together. SAP GRC Access Control handles provisioning, access requests, firefighter management, and workflow automation. MTC Skopos is a risk analysis and remediation tool that works across any system. Organizations use both: Skopos for analysis and cleanup, SAP GRC for automated workflows.

Should I run SoD analysis before implementing SAP GRC?

Yes. Running SoD analysis and remediation before configuring SAP GRC ensures you are not automating the provisioning of risky access. Cleaning roles first also means the GRC project starts from known conflict numbers instead of estimates.

How does MTC Skopos work alongside Pathlock?

MTC Skopos runs risk analysis across any system, including those outside Pathlock's scope. Use Pathlock for integrated provisioning and workflow on core systems, and Skopos for SoD analysis on satellite systems, legacy ERPs, and non-SAP environments.

What happens to MTC Skopos after SAP GRC goes live?

Most organizations keep Skopos for systems not covered by their GRC suite: regional SAP instances, legacy ECC systems, non-SAP ERPs, and warehouse systems. It stays as a complement to the integrated platform for the systems the suite does not reach.

Can I transfer my MTC Skopos ruleset to SAP GRC or Pathlock?

Yes. The SoD ruleset you build and validate in Skopos converts to SAP GRC or Pathlock format. The effort you put into defining risks, tuning false positives, and validating with business process owners carries over directly to your target GRC platform.

How long does it take to set up MTC Skopos for SoD analysis?

There is no implementation project. You install MTC Skopos, point it at your SAP data export, and run a full SoD and critical access analysis the same day. No server infrastructure, no GRC configuration, no workflow setup required.

Is MTC Skopos only for SAP systems?

No. MTC Skopos runs SoD analysis across SAP ECC, S/4HANA, and non-SAP ERPs. This makes it useful for organizations whose GRC suite covers core SAP systems but leaves gaps on legacy, regional, or non-SAP environments.

Should I measure my SoD risk before starting a GRC project?

Yes, and it changes how the project is scoped. Running an analysis first gives you the real conflict count, the ruleset already tuned against your authorization concept, and evidence of which risks are actually exercised, so the GRC implementation is sized on measured numbers rather than estimates. Skopos performs role-level and user-level analysis at the authorization-object level, produces a ranked remediation report, and lets you simulate changes before they go live. Organizations use this approach to maintain audit-ready SoD coverage on systems outside their GRC scope, and to clean their roles before any GRC rollout.

« All posts