What should you do if your computer behaves abnormally? Is malware running behind the screen? Has your Personally Identifiable Information (PII) or other financial data gone missing? If yes, your computer has been compromised and you need to initiate a personal incident response plan. It’s important to create one before the attack hits, as quick implementation is of vital importance.
The personal incident response plan is a set of some proactive measures created to handle security incidents that have occurred to your personal computer, laptop or mobile device. An effective personal incident response plan enables you to quickly and methodically identify the threat, mitigate the damage and reduce the cost of the cyberattack. The following sections will help you get a better understanding of personal incident response plans.
During specific attacks
In order to detect a malware attack, it’s important to be familiar with the symptoms of an attack. Some common symptoms include fake antivirus messages, unexpected software installs, your passwords not working as expected, frequent random popups, redirected Internet searches, unwanted browser toolbars, slower performance, computer programs open and running on their own, automatically duplicating files and denied access to files and folders.
In addition, your anti-malware software, Registry Editor or/and Task Manager may be disabled and can’t be restarted. Under such circumstances, knowing how to detect these nasty intrusions will help you determine how to fix the problem. Below are some potential attack scenarios and the solutions to get rid of them with minimum or no damage at all.
Ransomware is becoming more common. In these cases, once your Personally Identifiable Information (PII) or other sensitive data is locked up or encrypted by cyberpests, you will receive a ransom message asking for money in order to provide access and decrypt the data. To hide their (Read more...)
*** This is a Security Bloggers Network syndicated blog from Infosec Resources authored by Fakhar Imam. Read the original post at: http://feedproxy.google.com/~r/infosecResources/~3/o13PhE-9mUk/