MOBIUSI INCThis dataset contains microservice source-code cases involving flaws in identity propagation, permission checks, and tenant-isolation boundaries, with supporting details on service boundaries, identity flows, failure stages, and root causes. Each case also includes security impact, a repair explanation, fixed code, and regression test guidance for cloud-native application security reviews and authorization troubleshooting. It supports code SFT by helping models reason from source code and call chains to locate authorization failures and propose fixes.
Overview
Preview
Schema
| Field | Type | Description |
|---|---|---|
| file_name | string | File name |
| fixed_code | string | A corrected code snippet addressing the flaw in the source code. |
| root_cause | string | Explains the code logic, trust assumption, or omitted check that caused the authorization boundary to fail. |
| source_code | string | A microservice source-code snippet containing an authorization boundary flaw, provided as the input for analysis. |
| failure_stage | string | Specifies whether the failure occurs during identity extraction, identity propagation, permission evaluation, or a downstream call. |
| identity_flow | string | Describes how an identity or credential travels from the request entry point through the call chain to the permission check. |
| regression_test | string | Describes test scenarios for validating the fix and the expected authorization or tenant-isolation outcomes. |
| security_impact | string | Describes potential consequences such as unauthorized access, privilege escalation, or cross-tenant data exposure. |
| service_boundary | string | Describes the relevant service, interface, or component boundaries and their roles in the call chain. |
| repair_explanation | string | Explains how the fix strengthens identity propagation, permission validation, or tenant boundary checks. |
| authorization_check_point | string | Identifies the function, call site, or code stage where an authorization check should occur or currently occurs. |
| tenant_isolation_analysis | string | Explains whether the flaw enables cross-tenant access and how tenant identifiers are handled during validation and data access. |
Trust
Authorization Type
Proprietary - Commercial AI Training License (No Redistribution)
Commercial Use
Requires exclusive subscription or authorization contract (monthly or per-invocation charging)
Privacy and Anonymization
No PII, no real company names, simulated scenarios follow industry standards
Compliance System
Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs
FAQ
Post a request and let data providers reach out to you.
High-quality data, ready for your next AI breakthrough.
@dataset{Mobiusi2026,
title={Microservice Authorization Boundary Debugging and Root-Cause Analysis Dataset},
author={MOBIUSI INC},
year={2026},
url={https://www.mobiusi.com/datasets/7448e9486c52de1ce81537b97887fbe5?dataset_scene_id=19},
urldate={2026-10-21},
keywords={microservice security dataset,authorization boundary flaws,source code security audit,identity flow analysis,permission checks,tenant isolation,code reasoning,secure code repair},
version={1.0}
}Using this in research? Please cite us.