In this article
Social media can support mutual aid and access to information. It can also enable impersonation, data theft and misleading claims. Preparedness combines account protection, verification of requests and careful decisions about what to share.
A profile is not a verified identity
A photograph, an apparent seniority or common contacts can give confidence without establishing who controls the account. If a request is out of the ordinary, check it with the person or service through an already known channel. Don’t ask for an additional sensitive document just to conduct your own investigation.
An authentic account can also be compromised. A message from a loved one does not automatically authorize the transmission of code, money or information. Keep the possibility to confirm the request otherwise, especially when it is presented as urgent or secret.
Reducing actionable information
Check the people who see your posts, location and details about household routines. A photo can show a badge, address, or document in the background. Choose what has real utility for recipients and what can be shared later, in a more limited circle.
Members of the household may have different practices. Agree on a few simple rules about children’s pictures, absences and documents. The goal is not to monitor loved ones, but to prevent information that one person wanted to protect from being published by another.
Understanding the effect of trends
A repeated or highly commented publication is not an independent confirmation. Look at the origin, date, location, and ability to find the complete document. A screenshot may leave out the context for a decision.
Reactions and comments may give the impression of unanimous agreement. Before sharing, ask what is verified and what is an interpretation. For emergency instructions, look for the relevant service and territory rather than a message that has become popular.
Review invitations and offers of assistance
A group, training or service proposal may require more information than is necessary. Check the organizer, the role of the interlocutors, the conditions and the possible payment channel. A promise of security or privileged access does not replace these checks.
You can ask a question or refuse to transmit data without participating in a conflicting exchange. If the conversation becomes threatening, keep the useful elements and use the tools of the platform or competent services depending on the situation. Don’t try to infiltrate a group to prove an intuition.
Protect access to the account
Use the security features offered by the service, review sessions and prepare recovery methods. Limit the devices or applications that have access to the account to the necessary uses. A setting must remain understandable to the person who will have to maintain it.
If you think an account is compromised, use the official recovery path and notify contacts who may receive misleading requests. Do not pass on the received codes to an interlocutor who claims to solve the problem. Check support requests through official contact information.
Correct without amplifying
When a shared information is false or outdated, correct it clearly and indicate the useful reference. Avoid unnecessarily reposting personal data or misleading content in a capture that gives it a new audience. The correction should help recipients decide, not just show that the error has been spotted.
In a prep group, provide a check rule, moderation, and a way to remove a dangerous or outdated link. Responsibility should be clear and not rely on someone who is always available.
A simple check to practice
Take a fictional example of an urgent request. Identify the apparent account, the requested information, the independent confirmation channel, and what to do if the request is not confirmed. This small exercise develops a method without fabricating false profiles or misleading the members of the group.
References: Get Cyber Safe , Phishing Sheet · Check requests and their channels.