Mastodon

0 posts0 participants0 posts today

tuxwise(19/N) Let's now turn to the third question of the <a href="https://mastodon.de/tags/ThreatModelingManifesto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ThreatModelingManifesto</a>: 3. What are you going to do about it?It pays to first establish a few contraints for what you can do, in theory, by <a href="https://mastodon.de/tags/classifying" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#classifying</a> your <a href="https://mastodon.de/tags/assets" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#assets</a>. Again, for an individual human being, opposed to organizations or companies, it's nearly impossible to impose principles like <a href="https://mastodon.de/tags/ZeroTrust" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ZeroTrust</a> or <a href="https://mastodon.de/tags/NeedToKnow" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#NeedToKnow</a> on personal relationships, the closer they get.So, avoid recycling terms from popular, but less intuitive schemes: Fanciful intelligence labels like “top secret”, “confidential”, or “unclassified” do not tell you what goes into the respective box, and how to handle access to it.Add another column to your assets spreadsheet, label it "Classification", and pick a more human-centered approach for its values, like:<ul><li>For Your Eyes Only (FYEO)</li><li>Intimate</li><li>None Of Your Business (NOYB)</li><li>Shared</li><li>Public</li></ul>Let's briefly go through these suggestions:For Your Eyes Only (FYEO)Assets that are only accessible to, and controlled by nobody but you, because they need to be resilient, even in the face of the closest of your close people misbehaving. Preferably, these assets are kept publicly undetectable and unknown. When you are gone, these assets will be gone, too. FYEO does not make a good default class, though.Start of this thread: <a href="https://mastodon.de/@tuxwise/113503228291818865" translate="no" rel="nofollow noopener noreferrer" target="_blank">https://mastodon.de/@tuxwise/113503228291818865</a><a href="https://mastodon.de/tags/ThreatModeling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ThreatModeling</a> <a href="https://mastodon.de/tags/4D" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#4D</a>

Christof Schöch<a href="https://fedihum.org/@cnDuKeli" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@cnDuKeli</a> <a href="https://fedihum.org/@tcdh" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tcdh</a> The approach they used for <a href="https://fedihum.org/tags/classifying" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#classifying</a> the poems' function in the narrative were interesting, using <a href="https://fedihum.org/tags/LLMs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#LLMs</a>. Performance is pretty bad so far. Keli took up the call for <a href="https://fedihum.org/tags/openness" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#openness</a> about <a href="https://fedihum.org/tags/failure" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#failure</a> from a session this morning and showed that the different models are bad in different ways, which allowed the team (and us) to learn something about the models. I think that's great and valuable! <a href="https://fedihum.org/tags/ErrorAnalysis" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ErrorAnalysis</a> <a href="https://fedihum.org/tags/ConfusionMatrix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ConfusionMatrix</a> <a href="https://fedihum.org/tags/MajorityBaseline" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MajorityBaseline</a> <a href="https://fedihum.org/tags/DH2024" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DH2024</a>

🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸I have plenty more achievable goals for <a href="https://schizo.social" rel="nofollow noopener noreferrer" target="_blank">https://schizo.social</a> (like multi-account, or <a href="https://mas.to/tags/Calckey" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Calckey</a> support) but something I'd love to try is <a href="https://mas.to/tags/classifying" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#classifying</a> posts with <a href="https://mas.to/tags/machineLearning" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#machineLearning</a> <a href="https://mas.to/tags/tfidf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tfidf</a> I'd like to be able to define "labels" and then train it to identify those on the fly. Then either mute or highlight posts that <a href="https://mas.to/tags/classify" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#classify</a> highly. Not so much an <a href="https://mas.to/tags/algorithm" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#algorithm</a>, as a <a href="https://mas.to/tags/filter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#filter</a>.<a href="https://mas.to/tags/ai" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ai</a> <a href="https://mas.to/tags/ml" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ml</a> <a href="https://mas.to/tags/webDev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#webDev</a> <a href="https://mas.to/tags/classifier" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#classifier</a>

Recent searches

Search options

Administered by:

Server stats:

#classifying