Carbophile

joined 2 months ago
[–] Carbophile@lemmy.zip 1 points 1 month ago (2 children)

Hmmm, strange. It's working on my side.

[–] Carbophile@lemmy.zip 9 points 2 months ago (4 children)

Honestly, I'll take anything over those outsourced call centers at this point. Half of those representatives barely speak English.

 

Operations Security (OPSEC) is a space dedicated to discussing, sharing, and learning about operational security practices. Whether you are a business owner, a cybersecurity expert, or just a regular person, you can always benefit from a little extra OPSEC in your life.

We are proud to be the first OPSEC related community on Lemmy and we are rapidly growing.

You can find us here (!opsec@lemmy.zip).

 

Operations Security (OPSEC) is a space dedicated to discussing, sharing, and learning about operational security practices. Whether you are a business owner, a cybersecurity expert, or just a regular person, you can always benefit from a little extra OPSEC in your life.

We are proud to be the first OPSEC related community on Lemmy and we are rapidly growing.

You can find us here (!opsec@lemmy.zip).

[–] Carbophile@lemmy.zip 2 points 2 months ago

No, it should delete all system files. Those people don't deserve a computer.

[–] Carbophile@lemmy.zip 2 points 2 months ago (1 children)

"Cave Johnson, we're done here."

[–] Carbophile@lemmy.zip 17 points 2 months ago* (last edited 2 months ago) (1 children)

You can always forcefully shut it down while it's rebooting.

[–] Carbophile@lemmy.zip 3 points 2 months ago* (last edited 2 months ago) (3 children)

This is quite extreme. While it could be beneficial for some threat models, this was written as an example for the average Joe. OPSEC is not about having the best possible security as much as it is about having security that satisfies your threat model.

[–] Carbophile@lemmy.zip 4 points 2 months ago

It is unfortunately impossible to defend against time. What works today might not work tomorrow, but that doesn't mean you should give up because it might get compromised at some point in time. Establishing a clear threat model helps push that point in time farther away.

[–] Carbophile@lemmy.zip 58 points 2 months ago* (last edited 2 months ago) (5 children)

The backlash is extremely idiotic. The only two options are to store it in plaintext or to have the user enter the decryption key every time they open it. They opted for the more user-friendly option, and that is perfectly okay.

If you are worried about an outsider extracting it from your computer, then just use full disk encryption. If you are worried about malware, they can just keylog you when you enter the decryption key anyways.

64
submitted 2 months ago* (last edited 2 months ago) by Carbophile@lemmy.zip to c/privacy@lemmy.ml
 

Cross-posted from: https://lemmy.zip/post/18686329 (the first OPSEC community on Lemmy, feel free to join us)

Guide to Determining Your Threat Model

Creating a solid threat model is an essential step in improving your operations security (OPSEC). It helps you identify potential threats, assess their impact, and prioritize your defenses. Here’s a step-by-step guide to help you develop your own threat model.


1. Define Your Assets

First, list the things you want to protect. These might include:

  • Personal Information: Name, address, phone number, Social Security number, etc.
  • Financial Information: Bank account details, credit card numbers, financial records.
  • Digital Assets: Emails, social media accounts, documents, photos.
  • Physical Assets: Home, devices (computers, smartphones, etc.).

2. Identify Potential Threats

Next, think about who or what could pose a threat to your assets. Possible threats include:

  • Hackers: Individuals or groups looking to steal data or money.
  • Government Agencies: Law enforcement or intelligence agencies conducting surveillance.
  • Corporations: Companies collecting data for marketing or other purposes.
  • Insiders: Employees or contractors who might misuse their access.
  • Physical Threats: Burglars or thieves aiming to physically access your assets.

3. Assess Your Vulnerabilities

Identify weaknesses that these threats could exploit. Consider:

  • Technical Vulnerabilities: Unpatched software, weak passwords, outdated systems.
  • Behavioral Vulnerabilities: Poor security habits, lack of awareness.
  • Physical Vulnerabilities: Insecure physical locations, lack of physical security measures.

4. Determine the Potential Impact

Think about the consequences if your assets were compromised. Ask yourself:

  • How critical is the asset?
  • What would happen if it were accessed, stolen, or damaged?
  • Could compromising this asset lead to further vulnerabilities?

5. Prioritize Your Risks

Based on your assessment, rank your risks by considering:

  • Likelihood: How probable is it that a specific threat will exploit a particular vulnerability?
  • Impact: How severe would the consequences be if the threat succeeded?

6. Develop Mitigation Strategies

Create a plan to address the most critical risks. Strategies might include:

  • Technical Measures:

    • Use strong, unique passwords and enable two-factor authentication.
    • Keep your software and systems up to date with the latest security patches.
    • Use encryption to protect sensitive data.
  • Behavioral Measures:

    • Be cautious with sharing personal information online.
    • Stay informed about common scams and phishing tactics.
    • Regularly review your privacy settings on social media and other platforms.
  • Physical Measures:

    • Secure your devices with locks and use physical security measures for your home or office.
    • Store sensitive documents in a safe place.
    • Be mindful of your surroundings and use privacy screens in public places.

7. Continuously Review and Update

Your threat model isn’t a one-time project. Review and update it regularly as your situation changes or new threats emerge.


Example Threat Model

  1. Assets:

    • Personal Information (e.g., SSN, address)
    • Financial Information (e.g., bank accounts)
    • Digital Assets (e.g., emails, social media)
    • Physical Assets (e.g., laptop, phone)
  2. Threats:

    • Hackers (e.g., phishing attacks)
    • Government Agencies (e.g., surveillance)
    • Corporations (e.g., data collection)
    • Insiders (e.g., disgruntled employees)
    • Physical Threats (e.g., theft)
  3. Vulnerabilities:

    • Weak passwords
    • Outdated software
    • Sharing too much information online
    • Insecure physical locations
  4. Potential Impact:

    • Identity theft
    • Financial loss
    • Loss of privacy
    • Compromise of additional accounts
  5. Prioritize Risks:

    • High Likelihood/High Impact: Weak passwords leading to account compromise.
    • Low Likelihood/High Impact: Government surveillance leading to loss of privacy.
  6. Mitigation Strategies:

    • Use a password manager and enable two-factor authentication.
    • Regularly update all software and devices.
    • Limit the amount of personal information shared online.
    • Use a home security system and lock devices.