))
Bee SAFE, Not Sorry: Why Reporting Security Incidents at Yale is Mission-Critical and Time Sensitive
Manage episode 360988514 series 3395476
Treść dostarczona przez Wendy Battles/James Tucciarone. Cała zawartość podcastów, w tym odcinki, grafika i opisy podcastów, jest przesyłana i udostępniana bezpośrednio przez Wendy Battles/James Tucciarone lub jego partnera na platformie podcastów. Jeśli uważasz, że ktoś wykorzystuje Twoje dzieło chronione prawem autorskim bez Twojej zgody, możesz postępować zgodnie z procedurą opisaną tutaj https://pl.player.fm/legal.
One of the most important cybersecurity actions our Yale community can take is to report suspicious cyber activity right away to the Information Security Office.
This action is critical to get ahead of malicious actors trying to gain unauthorized access to the important work we do every day in support of the Yale mission. Your attention and response can potentially save Yale from serious financial, reputational, or operational impact.
When it comes to reporting incidents, we want you to “Bee SAFE, Not Sorry”, where SAFE stands for the four simple reminders to make reporting easy.
Listen to this episode and you'll learn:
▶️ Why you should report suspicious cyber activity
▶️ Why the timeframe within which you report an incident matters
▶️ An overview of the SAFE model, breaking down each of the components
▶️ How to report security incidents at Yale
▶️ Our buzzword of the day - "security incident"
*********
Calls to Action:
Ready to build your cyber muscles, outsmart cybercriminals and hone your reporting skills?
Here are 3 simple things you can do:
- Review Yale's Report an Incident page about how to report suspicious behavior.
- Register for Bee SAFE, Not Sorry events in April and May.
- Read about incident reporting in our Bee Cyber Fit spring newsletter and April cybersecurity tip.
Learn more about Yale Cybersecurity Awareness at cybersecurity.yale.edu/awareness
Never miss an episode! Sign up to receive Bee Cyber Fit podcast alerts.
23 odcinków
Udostępnij
