Computer systems and methods to protect user credential against phishing
Computer systems and methods to protect user credential against phishing with security measures applied based on determination of phishing risks of locations being visited, phishing susceptibility of users, roles of users, verification of senders of messages, and/or the timing of stages in accessing and interacting with the locations. For example, when a site is unclassified at the onset of being accessed by a user device, security measures can be selectively applied to allow the site to be initially viewed on the user device, but disallow some user interactions to reduce phishing risk. For example, a response to a domain name system (DNS) request can be customized based on a user risk level. For example, a message can be displayed without a profile picture of a contact of a user when the sender of the message appears to be the contact but cannot be verified to be the contact.
1. A computing device, comprising:
at least one microprocessor;
a communication device configured to communicate over internet; and
memory configured to store instructions which, when executed by the at least one microprocessor, cause the computing device to:
maintain a contact list of a user of the computing device;
store, at least for one contact identified in the contact list, a profile picture of the contact identified in the contact list of the user;
receive a message, the message identifying a sender of the message;
determine that the sender identified by the message corresponds to the contact identified in the contact list of the user;
determine a risk score of at least one of the computing device or user, wherein the risk score is based at least partially on an assessed skill level of the user;
responsive to the risk score exceeding a threshold, determine whether the contact has sent the message; and
present the message on the computing device, wherein the message is presented without the profile picture in response to the computing device failing to verify that the contact has sent the message, and presented with the profile picture in response to successfully verifying that the contact has sent the message.
2. The computing device of claim 1 , wherein the message is an email message; the message identifies the sender via a name in a from field of the email message; and the sender is determined to correspond to the contact based on the name matching with the contact in the contact list of the user.
3. The computing device of claim 1 , wherein the message is an email message; the message identifies the sender via a name in a reply-to field of the email message; and the sender is determined to correspond to the contact based on the name matching with the contact in the contact list of the user.
4. The computing device of claim 1 , wherein the message is an email message; the message identifies the sender via an email address in a from field or a reply-to field of the email message; and the sender is determined to correspond to the contact based on the email address matching with the contact in the contact list of the user.
5. The computing device of claim 1 , wherein the instructions which, when executed by the at least one microprocessor, cause the computing device further to:
analyze a header of the message in determining whether the contact has sent the message.
6. The computing device of claim 5 , wherein the instructions which, when executed by the at least one microprocessor, cause the computing device further to:
determine whether the header of the message includes a record of transmission by a server of a domain associated with an address of the sender of the message.
7. The computing device of claim 5 , wherein the instructions which, when executed by the at least one microprocessor, cause the computing device further to:
determine whether the message is from a domain associated with an address of the sender of the message based on information provided via sender policy framework.
8. The computing device of claim 1 , wherein the instructions which, when executed by the at least one microprocessor, cause the computing device further to:
verify whether the message has a digital signature of the contact in determining whether the contact has sent the message.
9. The computing device of claim 1 , wherein the instructions which, when executed by the at least one microprocessor, cause the computing device further to:
identify a trusted server that originates the message; and
communicate with the trusted server to verify an origin of the message in determining whether the contact has sent the message.
10. The computing device of claim 1 , wherein the instructions which, when executed by the at least one microprocessor, cause the computing device further to:
identify a trusted server that originates the message; and
verify that the sender identified by the trusted server has not been altered after the trusted server originates the message.
11. A method, comprising:
storing a contact list of a user of a computing device, including a profile picture of at least one contact identified in the contact list of the user;
receiving a message, the message identifying a sender of the message;
determining that the sender identified by the message corresponds to the contact identified in the contact list of the user;
determining a risk score of at least one of the computing device or user, including assessing a skill level of the user;
responsive to the risk score exceeding a threshold, determining whether the contact has sent the message; and
presenting the message on the computing device, wherein the message is presented without the profile picture in response to the computing device failing to verify that the contact has sent the message, and presented with the profile picture in response to successfully verifying that the contact has sent the message.
12. The method of claim 11 , wherein the determining of whether the contact has sent the message includes:
determining whether a header of the message includes a record of transmission by a server of a domain associated with an address of the sender of the message.
13. The method of claim 11 , wherein the determining of whether the contact has sent the message includes:
determining whether the message is from a domain associated with an address of the sender of the message based on sender policy framework.
14. The method of claim 11 , wherein the determining of whether the contact has sent the message includes:
checking whether a digital signature of the message corresponds to the contact.
15. The method of claim 11 , wherein the determining of whether the contact has sent the message includes:
identifying a trusted server that originates the message; and
communicating with the trusted server to verify an origin of the message.
16. The method of claim 11 , wherein the determining of whether the contact has sent the message includes:
identifying a trusted server that originates the message; and
verifying that the sender identified by the trusted server has not been altered after the trusted server originates the message.
17. A non-transitory computer storage medium storing instructions of a security application of a computing device, the security application having instructions which when executed on the computing device, cause the computing device to perform a method, the method comprising:
storing a contact list of a user of a computing device, including a profile picture of at least one contact identified in the contact list of the user;
receiving a message, the message identifying a sender of the message;
determining that the sender identified by the message corresponds to the contact identified in the contact list of the user;
determining a risk score of at least one of the computing device or user, including assessing a skill level of the user;
responsive to the risk score exceeding a threshold, determining whether the contact has sent the message; and
presenting the message on the computing device, wherein the message is presented without the profile picture in response to the computing device failing to verify that the contact has sent the message, and presented with the profile picture in response to successfully verifying that the contact has sent the message.
18. The non-transitory computer storage medium of claim 17 , wherein the message is an email message; the message identifies the sender via a field in a header of the email message; and the method further comprises:
matching content of the field in the header of the email message to a corresponding field in the contact list in determining that the sender corresponds to the contact identified in the contact list.
19. The non-transitory computer storage medium of claim 18 , wherein the field includes a name or an email address of the sender; and the field is a from field or a reply-to field in the header of the email message.
20. The non-transitory computer storage medium of claim 17 , wherein the determining of whether the contact has sent the message includes:
determining whether a header of the message includes a record of transmission by a server of a domain associated with an address of the sender of the message;
determining whether the message is from a domain associated with an address of the sender of the message based on sender policy framework;
checking whether a digital signature of the message corresponds to the contact;
communicating with a trusted server to verify an origin of the message; or
verifying that the sender identified by the trusted server has not been altered after the trusted server originates the message; or
any combination thereof.
21. The computing device of claim 1 , wherein the risk score is further based on a damage level potential of the computing device.