Performance Issue: Widespread locking of NetID accounts
Last Updated:
2019-08-13 19:30:02
Event:
2019-08-12 14:30:00
Status:
Closed
Brief Description:
Over the weekend of August 10-11, attackers caused a large number of NetID compromises; beacuse of the scale, some of our recovery processes are experiencing delays.
User Impact:
N/A
Workaround:
There is no workaround for this issue
Current Status:
Users continue to experience delays. We ask your patience.
Services Affected:
Authentication and Authorization
Subsites Affected:
My Extension Everywhere
Full Description:
Over the weekend of August 10-11, 2019, attackers tried to log into Cornell services using an extremely large number of NetIDs. Some of these accounts have been confirmed to be compromised. All of the compromised NetID accounts have been locked. Because of the scale of this attack, individuals trying to contact the IT Service Desk may experience delays getting through.
If you received a notification from Cornell IT Security, you can change your password at
https://netid.cornell.edu
If you changed your NetID password very soon after you were notified, it's possible you may have been locked out despite having changed your password. We apologize for the inconvenience. You will need to reactivate your account, but this should happen only once.
If you are enrolled in Google 2-Step Verification, it will have to be disabled before you can sign into your
account. Please contact the IT Service Desk for help with this. https://it.cornell.edu/support
It is also taking longer than usual for password changes or reactivations to reach Cornell G Suite accounts, and in turn for affected users be able to sign back in again.
If you received a notification from Cornell IT Security, you can change your password at
https://netid.cornell.edu
If you changed your NetID password very soon after you were notified, it's possible you may have been locked out despite having changed your password. We apologize for the inconvenience. You will need to reactivate your account, but this should happen only once.
If you are enrolled in Google 2-Step Verification, it will have to be disabled before you can sign into your
account. Please contact the IT Service Desk for help with this. https://it.cornell.edu/support
It is also taking longer than usual for password changes or reactivations to reach Cornell G Suite accounts, and in turn for affected users be able to sign back in again.
Timeline of Changes
| Description | Current Status | Date | Time |
|---|---|---|---|
| Over the weekend of August 10-11, 2019, attackers tried to log into Cornell services using an extremely large number of NetIDs. Some of these accounts have been confirmed to be compromised. All of the compromised NetID accounts have been locked. Because of the scale of this attack, individuals trying to contact the IT Service Desk may experience delays getting through. If you received a notification from Cornell IT Security, you can change your password at https://netid.cornell.edu If you changed your NetID password very soon after you were notified, it's possible you may have been locked out despite having changed your password. We apologize for the inconvenience. You will need to reactivate your account, but this should happen only once. If you are enrolled in Google 2-Step Verification, it will have to be disabled before you can sign into your account. Please contact the IT Service Desk for help with this. https://it.cornell.edu/support It is also taking longer than usual for password changes or reactivations to reach Cornell G Suite accounts, and in turn for affected users be able to sign back in again. | Users continue to experience delays. We ask your patience. | 2019-08-12 | 20:11:44 |
| Over the weekend of August 10-11, 2019, attackers tried to log into Cornell services using an extremely large number of NetIDs. Some of these accounts have been confirmed to be compromised. All of the compromised NetID accounts have been locked. Because of the scale of this attack, individuals trying to contact the IT Service Desk may experience delays getting through. If you received a notification from Cornell IT Security, you can change your password at https://netid.cornell.edu If you changed your NetID password very soon after you were notified, it's possible you may have been locked out despite having changed your password. We apologize for the inconvenience. You will need to reactivate your account, but this should happen only once. If you are enrolled in Google 2-Step Verification, it will have to be disabled before you can sign into your account. Please contact the IT Service Desk for help with this. https://it.cornell.edu/support It is also taking longer than usual for password changes or reactivations to reach Cornell G Suite accounts, and in turn for affected users be able to sign back in again. | Users continue to experience delays. We ask your patience. | 2019-08-12 | 17:07:27 |
| Performance Issue: NetID Account Password Resets and IT Service Desk Over the weekend of August 10-11, 2019, attackers tried to log into Cornell services using an extremely large number of NetIDs. Some of these accounts have been confirmed to be compromised. All of the compromised NetID accounts have been locked. Because of the scale of this attack, individuals trying to contact the IT Service Desk may experience delays getting through. If you received a notification from Cornell IT Security, you can change your password at https://netid.cornell.edu If you changed your NetID password very soon after you were notified, it's possible you may have been locked out despite having changed your password. We apologize for the inconvenience. You will need to reactivate your account, but this should happen only once. If you are enrolled in Google 2-Step Verification, it will have to be disabled before you can sign into your account. Please contact the IT Service Desk for help with this. https://it.cornell.edu/support It is also taking longer than usual for password changes or reactivations to reach Cornell G Suite accounts, and in turn for affected users be able to sign back in again. | Users continue to experience delays. We ask your patience. | 2019-08-12 | 17:06:18 |