Zum Hauptinhalt springen
Echtzeit-Radar & Feeds
Alle RSS Feeds ➔
👥 Community & Social
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Windows Tipps & SecurityGrafikkarte vor Überhitzung schützen: So geht’s(25.09.2026 um 08:00 Uhr)
••••••••••
Intelligence View
⚡ tsecurity.de Intelligence

Ethical considerations of working with Microsoft technologies

I’ve been working as a C# dev since 2010. I was 16 years younger back then, and the "ethical considerations" of anything were not really a topic I was interested in. I was young and stupid, but at least smart enough (or so I thought) to s…

0
↗ Quelle (dev.to)
Reagiere als Erste:r — dein Feedback zählt!

I’ve been working as a C# dev since 2010. I was 16 years younger back then, and the "ethical considerations" of anything were not really a topic I was interested in. I was young and stupid, but at least smart enough (or so I thought) to see that continuing my career in PHP and its related toolchains had no future.



Today, I am grappling with a question that every sane person earning a living by working with Microsoft technologies must ask: am I okay with this?






Big corporations are evil



If you thought this post was not going to get political, you thought wrong.



This is not a statement about Microsoft in particular, but a statement about the biggest corporations in the world.



It is not, however, a statement against capitalism and the free market. The counterarguments defending capitalism and the free market, I imagine, probably come from patriotic Americans who are sick in the head.



No, I’m not against capitalism and the free market—to an extent.



Economics teaches us that companies try their hardest to achieve a monopoly. It’s a logical conclusion and a well-researched fact, not something we have to moralize about. Companies compete to maximize profits and long-term economic rent.



But when you’re one of the biggest corporations in the world, you have more tools at your disposal. You break rules, you crush the competition, and you get involved in politics. All to achieve a monopoly. Anyone defending big corporations is either someone whose job is to do exactly that—like someone from PR—or someone insane.



Have you ever met someone like that? That 25-year-old woman from HR who convinced herself that her life finally has meaning because she works for JPMorgan? She worships the brand like it’s some sort of religion. And it’s not just a professional mask; it’s her own tragically neurotic personality maintaining the brand worship in her personal life as well. And she’s not alone.



On the other hand, there are people who refuse to touch anything MS-related. This was confusing to me at first—it’s software, just code, so what are you doing? What are you trying to prove?



Some people do this for the wrong reasons, like refusing to touch anything that isn't open-source, or simply avoiding anything MS-related because "MS is bad" because Steve Ballmer once shat on Linux, or because Word once crashed on them.

But those who do it for the right reasons have a point. Working with tools created by an evil entity means you are part of the problem.



But... what if I build the right thing with the evil tool? What if tools made by evil can be used for good? Is it really that morally wrong to use tools made by evil?



Maybe just a little. I mean, we’re in the software development world, not the weapons manufacturing industry, where the questions are much harder to ask and the answers much harder to find. I imagine someone from Heckler & Koch stumbling upon this article by accident, reading the heading, and chuckling at the absurdity of it.



Using Visual Studio, VS Code, programming in C#... yeah, those are tools made by an evil company. Using them means we are contributing to the success of that company.



Can I live with it? Yeah. But I’m not going to deny the fact that a tiny bit of my moral integrity is being suppressed for my own well-being and that of my family.






It's good



Now comes the opposite view.

The ecosystem of MS tools is just... good. Even worse, it’s the best I’ve ever worked with. And I’ve tried a lot of different ecosystems and toolchains: PHP, C, C++, Java, Python, Node.js...



Don't get me wrong, back in 2010, MS technologies sucked. We had WebForms—a website framework that was absolutely horrible to work with. Visual Studio sucked too. In 2026, it’s a completely different universe; MS sidelined the horrible black box called .NET Framework, making the new framework open-source and cross-platform.



Especially when combined with Azure, the entire MS ecosystem is just great to work with, and it has no equal. People who complain about MS stuff not working just aren't seeing the side of the software development world where MS is actually doing a lot of good.



It doesn’t change the fact that MS as a whole is evil—like a multi-headed hydra—but the head responsible for engineering toolchains, the ecosystem, and developer support is definitely a very good, well-behaved head.






Summary




  • MS is evil. Using tools made by MS means you’re contributing to their success. Denying this is stupid.


  • However, the ecosystem of tools is very good—probably the best. Denying this is also stupid.


1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Remote Code Execution (RCE) Defense
Syntax validiert (0 Fehler)
title: Detect Exploitation - Ethical considerations of working with Microsoft technologies
id: cf6f6d85-27d9-4448-97d8-be658df6f78a
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-26
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access
Syntax validiert (0 Fehler)
rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-26"
        description = "YARA Signature for "
    strings:
        $str = "Ethical considerations of work" ascii wide
    condition:
        any of them
}
Syntax validiert (0 Fehler)
index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Ethical considerations of working with M")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count
Syntax validiert (0 Fehler)
message: "*Ethical considerations of working with M*"
Syntax validiert (0 Fehler)
CommonSecurityLog
| where Message has "Ethical considerations of working with M"
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

2. Cyber Threat Intelligence & Forensik

CTI Threat Relationship Graph4 Knoten / 3 Relationen
CVE / Incident Software MITRE ATT&CK CWE Weakness IoC
🎯
MITRE ATT&CK Matrix Navigator 14 Taktiken
Reconnaissance
-
Resource Development
-
Initial Access
Execution
Persistence
-
Privilege Escalation
Defense Evasion
Credential Access
-
Discovery
-
Lateral Movement
-
Collection
-
Command and Control
Exfiltration
-
Impact
tsecurity.de Cognitive Threat RAG
Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich Ethical considerations of working with M.... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen
  • 1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
  • 2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
  • 3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.
🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC
Ähnliche Beiträge
🔍 Verwandte News

Auch interessante Nachrichten Ethical considerations of working with Microsoft technologies

Thematisch verwandte Begriffe: Ethical, considerations, working, with · 6 Treffer

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Laden...

Beiträge werden geladen ...

Laden...

Videos werden geladen ...

Zum Aktualisieren ziehen
ZERO-DAY CVE-2026-88003 | InvoicePlane is a self-hosted open source application for managing invoi…
Advisory →
tsecurity.de Icon
Offline-Lesen, Eilmeldungen & 0ms Ladezeit

Installiere tsecurity.de direkt auf deinen Home-Bildschirm für das ultimative Vollbild-Magazinerlebnis ohne Browser-Leisten.

Nächster Beitrag