How can we help you?
Search our documentation or browse categories below
This help center covers installation, data source setup, ruleset management, risk analysis, simulation, and remediation in MTC Skopos. Browse the categories below, or use the search bar above to look across every article.
New to the tool? Start with Installation, connect a data source, then run your first user analysis. If you plan to drive Skopos from an AI assistant via the Model Context Protocol, see the MCP server section.
Browse All Categories
Getting Started
Installation, system requirements, and first launch.
4 articles
Data Sources
Connect to SAP systems, import files, and manage your data sources.
4 articles
Rulesets
Load, create, and understand risk definition rulesets.
3 articles
Browsing Data
Explore users, roles, and system information from your data sources.
3 articles
Risk Analysis
Run user and role analyses to identify access risk conflicts.
4 articles
Simulation
Test what-if scenarios before making changes in your SAP system.
2 articles
Remediation
Generate and manage recommendations for resolving access risks.
3 articles
AI Assistant
Use AI to analyze risks, generate audit findings, and get remediation advice through natural language.
4 articles
Reports & Export
Export analysis results and import previous reports.
3 articles
Data Integrity
Tamper-proof log signing, signature verification, and Bring Your Own Key (BYOK) for audit evidence.
5 articles
MCP Server
Integrate MTC Skopos with AI assistants using the Model Context Protocol.
3 articles
Reference
Troubleshooting guides and technical reference.
1 articlePopular topics
- Installing MTC Skopos on Windows: signed installer, system requirements, and SmartScreen handling for enterprise deployments.
- Connecting to a remote SAP system: pull authorization data live from S/4HANA or ECC over RFC.
- Importing SAP data from files: upload extracted tables when a remote connection is not available.
- Loading a ruleset: use the built-in MTC ruleset or import a custom CSV.
- Running a user analysis: identify SoD conflicts and critical access by user, with did-do filtering against actual transaction history.
- Running a role analysis: flag conflicts at the role level before assignment to users.
- Generating remediation recommendations: produce role redesign suggestions that resolve conflicts without breaking access.
- Exporting reports and verifying signed evidence: share findings with auditors and prove the file has not been tampered with.
Need more help?
If you cannot find an answer in the articles above, open the chat widget in the bottom-right corner of any page to reach the team directly. The blog goes deeper on SAP authorization design, ruleset construction, and remediation strategy with worked examples, and the FAQ covers licensing, deployment, and pricing questions.