SBC Medical: define the data and access scope for each incident
Incidents reported by SBC Medical involve company-managed databases and accounts at a service provider. This analysis proposes an assessment connecting each access boundary to the data and evidence of containment.
Auf Portugiesisch lesenIn this article
By Pentesty
Establish what the statement supports
The SBC Medical statement dated November 18 reports access to company-managed databases on November 16 and notification that day about unauthorized access to clinic accounts on the Tribeau service in Japan. The basic-personal-information category lists 1,624,000 individuals and records from 2010 to 2023. Causes and scope remain under investigation in the statement. The record dates do not establish how long access lasted.
That assessment is the company’s. The filing provides a public reference against which to check the account; technical acceptance of remediation depends on evidence from the environment. Pentesty’s proposal starts by turning each known boundary into a verifiable question and keeping unanswered questions visible to the people responsible for the decision.
Create a record for each control boundary
Choose a service and identify who administers the application, controls the database and grants access to the provider dashboard. These roles may belong to different teams. Also record which operator can stop an integration and who can authorize its return, so the decision has a clear route through the organization.
Describe the reach of each identity used in that operation. A booking administrator account needs documented permissions, dependencies and an accountable owner. Database access requires another record with its own components and evidence. Connect the two records when a dependency is demonstrated, without assuming that they share a cause.
The analysis of incident scope at Iris Plaza complements this exercise. Here, each record should allow another reviewer to identify the exact system examined, the account set and the part of the operation that remained outside the assessment sample.
Connect the data to its origin and time range
Build a working table recording the dataset origin, covered period, field categories and person responsible for confirmation. Specify the unit behind each number: people, accounts, requests or form entries. Keep possible overlap visible until a reconciliation supports a unique count and explains exactly what population that count represents.
Use this map to review which historical data remains reachable by the application or identities under assessment. The team needs to explain the purpose of that access and the retention rules applicable to its environment. Coordinate any change with the owners and preserve evidence needed for the investigation before performing cleanup or migration.
Require specific evidence for each containment action
Agree with the operator on a synthetic account and a legitimate booking operation for the authorized exercise. After a planned invalidation, record whether the previous credential fails and approved access still works. Retain the time, test identity, observed outcome and person who checked the execution so the result can be reviewed.
Request a separate outcome for sessions, tokens and integrations along the assessed path. A password-change statement should identify exactly what was checked. When the provider cannot supply evidence, retain that component as outstanding work, with an accountable owner and an explicit condition for resuming the assessment.
The review of provider credentials and integrations offers additional questions about the reach of each identity. Include verification of legitimate functionality after the change. Containment may affect services differently when they use human accounts, automation identities or persistent connections.
Deliver an acceptance record another person can review
Bring the scope, completed actions, evidence and exceptions together in a closure record for each system. Identify who accepts the result and which limitations accompany that decision. Outstanding work at a third-party service should remain attached to its own record even when another team has completed the task under its control.
Agree on another check when a permission, integration or data location changes. Use the record to guide retesting and updates to communications about the environment. This process gives leadership a concrete view of what was demonstrated and which work still requires ownership, evidence and follow-through.
Frequently asked questions
Can the numbers in different categories be added together?
First record each dataset’s unit and origin. A unique count requires reconciliation and evidence about possible overlaps, as well as a clear definition of the population being examined.
Does a dataset period show when the attack began?
A record period describes its time reference. Establishing the duration of access requires evidence of activity and a clear account of the limits of the available collection.
Does a password change complete access verification?
Define and test the action’s scope in the authorized environment. Record separate outcomes for credentials, sessions, tokens and integrations, including any part for which evidence is still unavailable.
Which document supports the facts in this analysis?
A company statement filed with the SEC supports the facts used here. Pentesty’s assessment proposals require defined scope and acceptance criteria for each environment.
Sources and references
The editorial starting point was the BleepingComputer report, published November 19. We checked the facts used here against the SBC Medical statement, dated November 18 and filed on EDGAR. The assessment exercises and acceptance criteria are Pentesty’s own analysis.
Original Pentesty analysis, published November 19, 2026. The proposed scenarios are editorial guidance, with scope and validation to be defined for each environment.