What security measures failed in the IBM testing environment?

Question

Accepted Answer

The incident was traced to unauthorised access to an IBM-managed testing dataset, but the specific failed security measures were not disclosed

SLA said the breach originated from unauthorised access to a dataset used in vendor development and systems integration testing inside an IBM-managed testing environment for STARS and ELS. Investigators found the dataset was supposed to include only mock and anonymised records, but it later contained real personal data including names, NRIC numbers and past property addresses for about 70,000 people. SLA also said the affected testing environment is separate from its live operational systems, while STARS and ELS ownership and lodgment records remain secure, but it has not publicly identified which particular controls failed.
SLA identified the root cause as unauthorised access to a testing dataset
SLA attributed the incident to unauthorised access to a dataset created for vendor development and systems integration testing. The dataset was first created in 1998 and was updated periodically, and preliminary checks indicated it was intended to hold only mock and anonymised records. Later checks found it included real personal information, including NRIC numbers and past property addresses for around 70,000 individuals.
The dataset’s contents did not match its intended mock and anonymised purpose
The key discrepancy was that the dataset was meant to contain mock and anonymised records for testing, yet it was found to contain real personal data. That included names, NRIC numbers, and past property addresses, which are precisely the types of identifiers that would typically be excluded from testing datasets if anonymisation and data masking were functioning as intended. SLA did not state which step in the dataset creation or handling process allowed real data to be present.
IBM removed access to stop further unauthorised entry
To limit additional exposure, IBM revoked access to the compromised system. This action was taken specifically to prevent further unauthorised entry after the incident was identified. SLA did not provide technical detail on what access pathway was exploited, or which access control or authentication mechanism was misconfigured.
SLA has not disclosed the exact controls that failed
SLA has not yet disclosed when the breach occurred or how many affected individuals have been contacted, and it did not specify which security measures failed. It did not name any particular control such as access permissions, network segmentation, encryption, monitoring and alerting, or account management. As a result, the only explicitly confirmed failure point is the occurrence of unauthorised access within the IBM-managed testing environment.

Reading history

Hide →

This history is cleared when the page is closed.

What security measures failed in the IBM testing environment?

Loading

Was this article helpful?

Helpful

Not helpful

Report an issue

1

0

0

Share with friends