Skip to content

content: clarify phishing awareness guidance on account claims and channel scope#445

Open
tim-sha256 wants to merge 1 commit intosecurity-alliance:developfrom
tim-sha256:patch-1
Open

content: clarify phishing awareness guidance on account claims and channel scope#445
tim-sha256 wants to merge 1 commit intosecurity-alliance:developfrom
tim-sha256:patch-1

Conversation

@tim-sha256
Copy link
Copy Markdown

Summary

  • clarify that labels such as “Official”, “Support”, “will never DM first”, and platform status indicators are not proof of legitimacy
  • recommend verifying identities only through links listed on the organization’s official website
  • clarify that teams should explicitly state which platforms are not used, not only which channels are official

Closes #443

Validation

  • reviewed wording for tone and consistency with existing content
  • verified changes are limited to docs/pages/community-management/overview.mdx

…annel scope

Clarify that profile labels and platform status indicators are not proof of legitimacy, and state that unsupported platforms should be explicitly identified.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Content(update): Improve phishing awareness guidance around DM claims and official channels

1 participant