PadhaikoAll subjects

Past exam question: 2081 Chaitra (Regular), Q3(c)

Communication English · 6 marks

Open in the Padhaiko app

Topic: Research Proposals, Research Reports & Technical Reports

Question

Prepare a report of a case study of a cybersecurity breach and its consequences. Write abstract, finding and discussion parts only.

Solution

Planning and Case Study Framework:

Complete Model Report Sections:

Case Study Report: Telecom and Payment Gateway Cybersecurity Breach
AbstractExecutive summary of the breach incident and broader consequences

ABSTRACT

On September 12, 2024, ConnectNepal Telecom suffered a critical data breach affecting its subscriber registry and integrated mobile wallet payment ecosystem. The intrusion originated through a compromised API credential belonging to an external third-party software vendor that managed billing analytics. Advanced persistent threat (APT) actors leveraged the unsegmented vendor connection to pivot into the telecom's internal core database, exfiltrating 1.2 million customer records containing phone numbers, hashed passwords, citizenship identification scans, and detailed call data records (CDRs).

Emergency incident containment protocols isolated the billing gateway within four hours, but forensic analysis revealed that unauthorized reconnaissance had persisted undetected for 28 days prior to trigger alerts. The incident caused substantial brand erosion, forced an immediate mandatory credential reset across all subscribers, and incurred regulatory fines of NPR 20 million levied by the telecommunications authority. This case study demonstrates that perimeter defenses are ineffective when third-party software supply chains remain unmonitored.

FindingsForensic technical evidence, chronology, and impact metrics

FINDINGS

A joint forensic audit conducted by internal security teams and external cyber defense specialists documented the following technical findings:

1. Infiltration Vector and Supply-Chain Entry:
The attackers breached an off-site web server operated by "SmartBill Ltd", a contracted third-party software vendor. Using hardcoded, unrotated administrative API credentials embedded in the vendor's synchronization scripts, the attackers established an authenticated session directly into ConnectNepal's internal billing server on August 15, 2024.

2. Lateral Movement and Internal Reconnaissance:
Because the API connection lacked network micro-segmentation and IP-whitelisting constraints, the threat actors navigated laterally from the billing subsystem into the high-security customer identity database using automated SQL enumeration scripts over a period of three weeks.

3. Scope of Compromised Information:
- Customer Identity Records: Exactly 1,240,000 subscriber profiles were exfiltrated via stealthy, compressed HTTPS POST requests disguised as regular web analytics telemetry.
- KYC Document Scans: Over 180,000 scanned national identity cards and passports stored in an unencrypted S3-compatible local bucket were downloaded.
- Financial Transaction Ledgers: Core financial wallet balances remained intact, but payment transaction metadata for July and August was intercepted.

4. Operational Consequences:
- Telecom portal and recharge services were voluntarily shut down for 18 hours to perform containment and credential revocation.
- Customer support channels were overwhelmed by over 80,000 panicked consumer inquiries in the first 48 hours following public disclosure.
- Telecommunications regulatory authorities launched a formal statutory inquiry, imposing an initial non-compliance fine of NPR 20 million.

DiscussionRoot cause evaluation, governance shortcomings, and lessons learned

DISCUSSION

The security catastrophe at ConnectNepal Telecom offers profound lessons regarding the vulnerabilities inherent in modern interconnected enterprise architectures:

First, the root vulnerability lay in the implicit trust granted to third-party vendor integrations. The organization maintained rigorous perimeter firewalls, yet permitted external vendor software to communicate directly with internal production databases without continuous mutual TLS verification or strict API payload validation. In zero-trust architecture, third-party connections must always be treated as untrusted, isolated within segregated DMZ networks, and subjected to strict least-privilege access rules.

Second, the failure of defense-in-depth principles was evident in data storage hygiene. Sensitive KYC identity documents and subscriber databases were stored without encryption at rest. Had robust AES-256 field-level encryption been applied to personal identifier tables, the exfiltrated database files would have remained unreadable and useless to the attackers.

Third, the 28-day dwell time highlights inadequate Security Information and Event Management (SIEM) detection capabilities. The volume of outbound encrypted traffic generated by the exfiltration should have triggered automated behavioral anomaly alerts. Telecommunication operators must invest in automated behavioral baseline monitoring and strict supply-chain vendor risk auditing to prevent peripheral vendor compromises from crippling national digital infrastructure.

Answer:

The case study provides:

  1. Abstract: Synthesizes the supply-chain intrusion into ConnectNepal Telecom, the 1.2 million customer record compromise, and the resulting financial and regulatory fallout.
  2. Findings: Details the technical breach timeline, third-party API vector (SmartBill Ltd), lateral movement, and exact data exfiltration metrics.
  3. Discussion: Analyzes the critical failures in third-party trust management, unencrypted data storage at rest, and delayed SIEM anomaly detection, establishing key principles for zero-trust architecture.

All past exam questions for Communication English