Fw opsec#142
Closed
mattaereal wants to merge 9 commits intodevelopfrom
Closed
Conversation
…o fw_opsec Updating fw_opsec to match develop latest updates
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Hi @mattaereal, Following typos were found in the pull request:
ℹ️ Here's how to fix them:
|
|
|
||
| ## Web3-Specific Travel Security | ||
|
|
||
| 1. Use hardware wallets for storing crypto assets and keep them physically secure |
Contributor
There was a problem hiding this comment.
Recommend not traveling with hardware wallets if they are not needed throughout duration of travel
| 2. Be cautious about revealing cryptocurrency holdings or involvement in high-value projects | ||
| 3. Consider using duress passwords or accounts if traveling to high-risk regions | ||
| 4. Be aware of targeted attacks at crypto conferences and events | ||
| 5. Establish specific protocols for transaction approvals while traveling |
Contributor
There was a problem hiding this comment.
Recommend reducing as much access to wallets as possible during travel
| The goal of social engineering defense is not just to prevent specific attacks but to build organizational resilience: | ||
|
|
||
| 1. Foster a security culture where questioning unusual requests is encouraged, not penalized | ||
| 2. Develop and practice "security skepticism" as a valued trait |
Contributor
There was a problem hiding this comment.
Suggested change
| 2. Develop and practice "security skepticism" as a valued trait | |
| 2. Develop and practice "security skepticism" as a valued trait. Always question and be aware of the limits of the organization's current security measures |
| 2. Classify these assets based on value and criticality to operations | ||
| 3. Implement appropriate security controls based on risk levels | ||
| 4. Regularly audit security practices and adapt to emerging threats | ||
|
|
Contributor
There was a problem hiding this comment.
possible add:
- Understand wallet risk levels based on frequency of signing and public profile
| 3. Use password managers to maintain strong, unique passwords across services | ||
| 4. Enable full-disk encryption on all personal devices | ||
| 5. Install and maintain reputable security software | ||
|
|
Contributor
There was a problem hiding this comment.
- Check system settings, enabling security features where necessary
| This section covers the following aspects of Web3-specific operational security: | ||
|
|
||
| 1. [Wallet Security](./wallet-security.md) - Securing cryptocurrency and NFT wallets | ||
| 2. [Smart Contract Operational Security](./smart-contract-opsec.md) - Operational considerations for deploying and managing smart contracts |
Contributor
There was a problem hiding this comment.
I can't seem to find this file on dev or this branch
Contributor
There was a problem hiding this comment.
just realized this branch is a draft
Collaborator
Author
|
I am still rethinking all of these. I probably will commit to an entire restructuring because there's something that seems a little bit off to me. This is not how I place Opsec in my mind right now. I'll post here a new structure and ask what you and others think! |
Collaborator
Author
|
I'm closing this PR since this was already merged along with other PR/push to dev. @ElliotFriedman, if you want, you can send these suggestions as a separate PR directly to develop, otherwise, I'll try to manually update them myself later |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First re-structuring. Nothing fancy. It's a draft, and I'll possibly re-write it entirely.