Skip to main content
Back
IntrusionAWS · Google Cloud
1 min read

Former Cisco engineer deletes 456 Webex virtual machines

Victim
Cisco Webex Teams
When
Sep 24, 2018Disclosed Aug 26, 2020
Entry
An AWS key still worked after resignation.

Five months after leaving Cisco, a former engineer used an AWS key that still worked to access the infrastructure behind Webex Teams. He deleted 456 virtual machines. More than 16,000 accounts lost service for up to two weeks.

What happened

Reported activity
Former engineer
Internet
Cisco AWS
Webex Teams

Incident overview / Cisco Webex Teams

  1. 1

    A former engineer returns

    September 24, 2018

    The government says the former engineer used his AWS key from his own Google Cloud project to access Cisco’s environment. He had left Cisco in April.

  2. 2

    Webex loses virtual machines

    September 24, 2018

    The engineer admitted that his actions deleted 456 virtual machines supporting Webex Teams. Over 16,000 accounts were shut down for up to two weeks.

Impact

More than 16,000 Webex Teams accounts lost service for up to two weeks. Cisco spent about $1.4 million in employee time on recovery and refunded customers more than $1 million.

Could this have been prevented?

Revoke credentials a departing engineer can still use

Include cloud access keys in offboarding. Invalidating the specific AWS key before September 24 would have removed the access path documented in court. Which AWS identity held it remains unknown.

Incident control assessments

0
Prevented
0
Contained
2
Not covered

How it could have been prevented

The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.

Reported activity
Former engineer
Internet
Cisco AWS
Webex Teams

Incident overview / Cisco Webex Teams

1 · A former engineer returns

1 Not covered

2 · Webex loses virtual machines

1 Not covered

Key facts

  • The engineer resigned in April 2018.
  • The sentencing memorandum traces the September access to his own Google Cloud project.
  • Cisco spent about $1.4 million in employee time on recovery.
  • The Justice Department says the incident did not compromise customer data.

Sources

Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.

  1. 1.
    United States v. Ramesh, Government’s Sentencing MemorandumU.S. Attorney’s Office, Northern District of California · Dec 2, 2020 · Vendor reportPage 2 identifies the AWS key, personal Google Cloud project, employment dates and deletion.
  2. 2.
    San Jose Man Pleads Guilty To Damaging Cisco’s NetworkU.S. Department of Justice · Aug 26, 2020 · Vendor reportDetails of the guilty plea, virtual machine count, interruption to customers and recovery costs.
  3. 3.
    San Jose Man Sentenced To Two Years In Imprisonment For Damaging Cisco’s NetworkU.S. Department of Justice · Dec 9, 2020 · Vendor reportConfirms the sentence, affected infrastructure and absence of customer data compromise.

The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.

More cloud attack breakdowns

All breakdowns