> For the complete documentation index, see [llms.txt](https://cybersecurity-cloud-and-it-notes.gitbook.io/kyles-cybersecurity-cloud-and-it-gitbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cybersecurity-cloud-and-it-notes.gitbook.io/kyles-cybersecurity-cloud-and-it-gitbook/wgu-network-engineering-and-security/ethics-in-technology/computing-and-technology-ethics-engaging-through-science-fiction-textbook/chapter-6-professional-ethics/6.2-professions.md).

# 6.2 PROFESSIONS

Alright! Let’s make this lean and impactful using the **Pareto principle**—focusing on the 20% of content that delivers 80% of the understanding—while making it fun and ADHD-friendly. Here we go!

***

#### 🚀 PROFESSIONS: CYBER EDITION 🚀

**What You Need to Know (20% with 80% of the Value):**

1. **Core Traits of Professions**: Understand what makes an occupation a profession and how this matters for technology.
2. **Role of Codes & Regulations**: Learn how professional codes of ethics interact with law and shape responsibilities.
3. **History of Professionalization**: Key moments in tech professionalization and how it impacts cybersecurity.

***

#### **6.2.1 WHAT IS A PROFESSION?**

Let’s break down **Greenwood’s 5 Core Characteristics**—this is the **20% that explains what makes a job a profession**:

1. **Body of Knowledge**: Professionals have deep academic + practical expertise. In cybersecurity, think of knowing **network security protocols** (theory) and **penetration testing** (practice).
2. **Authority**: You’re not just providing a service—clients rely on your expertise. Imagine a company trusts your judgment as a **cybersecurity consultant** to protect them from cyber threats.
3. **Privileges by the Community**: Professions often require **licenses** or **certifications**. In software engineering, some jurisdictions (like Ontario) need a license for official “software engineers.” For cybersecurity, certifications like **CISSP** show you meet industry standards.
4. **Code of Ethics**: These are the **guardrails**—ensuring you don’t exploit your professional power. For example, you can't use your **penetration testing** skills for malicious purposes.
5. **Professional Culture**: Beyond skills, professions have a unique culture—**common terms**, **values**, and **memes**. Cybersecurity pros have their own subculture, from jokes on **r/cybersecurity** to using shared tools like **Burp Suite**.

#### **Why Does This Matter?**

* Professions are a **social contract**: You get authority and trust, but you must follow ethical guidelines.
* This is **key** in cybersecurity—trust is everything when handling sensitive data.

***

#### **6.2.2 HISTORY OF PROFESSIONALIZATION**

Key **20% events** that shaped professional ethics:

* Late **19th Century**: Engineers form professional societies to establish themselves as more than just employees—leading to groups like **IEEE** (1884), which included tech giants like **Tesla** and **Edison**.
* **Codes of Ethics (1912)**: After major **failures** in bridges and factories, societies like **IEEE** and **ASCE** established codes to prevent misuse of engineering expertise. This is the **birth of professional ethics**—to protect public safety.
* **NSPE (1934)**: The **National Society of Professional Engineers** created one of the oldest engineering codes, emphasizing things like **anti-bribery** and **public safety**. The goal? To maintain **trust** in those who design critical infrastructure—think bridges, airplanes, and power systems.

**Key Point:**

* **Cybersecurity has parallels**: Many certification bodies like **ISC2** or **ISACA** were born to formalize ethical guidelines for security pros, especially to avoid public breaches and misuse of skills.

***

#### **6.2.3 PROFESSIONALIZATION IN COMPUTING**

**Software Engineering** is a **grey area** between trade and profession. Here's the **20% that matters**:

* **Established Traits**: Theoretical knowledge (e.g., **algorithms**), codes of ethics (e.g., **ACM/IEEE Code**), and professional culture (like **memes** on r/ProgrammerHumor).
* **Privileges & Authority**: Licensing varies by location (e.g., Canada vs. the U.S.). Software engineers often lack the authoritative role that civil engineers have. In **cybersecurity**, it's similar—without certification, you may be seen as a "techie for hire."

**Why It Matters**: As cybersecurity professionalization grows, we need standards like **penetration tester licenses** to avoid “**guns for hire**” situations where people do unethical hacking because they lack professional boundaries.

***

#### **6.2.4 PROFESSIONS AND THE LAW**

Professional organizations shape **how technology interacts with law**. Here's the **20% that matters**:

* **Professional Self-Regulation**: Tech professions are often regulated **internally** to keep government laws from being too rigid. Example: The **IEEE** creating standards for data privacy before regulations like **GDPR** caught up.
* **Policy Lag**: Tech evolves faster than law, creating **“policy vacuums”**. Example: The rise of **Airbnb** and **Uber** led to conflicts over local regulations—highlighting why ethics codes are needed before laws catch up.

**Cybersecurity Application:**

* Regulations like **GDPR** arose because companies used data without consent. **Proactive self-regulation** by cybersecurity professionals helps create trust, making laws like GDPR more informed.

***

#### **SIDEBAR: AUTONOMOUS CARS**

**Metaphor in Law**: Imagine a **self-driving car** and a robot driving a car—similar tech, but different **legal perceptions**. These differences impact how we regulate tech. This metaphor explains why misapplied standards (like treating **email privacy** like sealed mail) can lead to **regulatory gaps**. In cybersecurity, misunderstandings in how we define “**data privacy**” lead to inconsistent protections.

***

#### **MAIN TAKEAWAYS** (20% of Knowledge with 80% Impact):

1. **Profession Traits**: Deep knowledge, authority, community privileges, ethical codes, and culture.
2. **History of Professionalization**: Born out of **public safety failures**, growing with formal codes of ethics.
3. **Computing as a Profession**: Software engineering and cybersecurity are on the way but lack universal licensing.
4. **Interaction with Law**: Ethical self-regulation bridges gaps until laws catch up. Always **be proactive**—ethical action influences regulations before they become law.

***

#### **REFERENCE**

* Burton, E., Goldsmith, J., Mattei, N., Siler, C., & Swiatek, S.-J. (2023). *Computing and Technology Ethics: Engaging Through Science Fiction*. MIT Press.

***

This is a focused summary with the essential 20% that provides 80% of the insights! Let me know if this style works for you or if you need adjustments to make it even more digestible! 😊