By Prince Damte
Introduction
When I began my interdisciplinary studies program, I did not yet have the language to describe what I was becoming. I knew I was interested in technology. I knew I had moved from Ghana to the United States with a hunger to build something meaningful from my education. But it was not until I began connecting coursework across disciplines — writing, critical thinking, ethics, information technology, and security — that I understood what kind of professional I was training to be. This portfolio represents the convergence of those disciplines into three marketable skills: network security and defense, threat analysis and incident response, and ethical hacking and penetration testing. These skills did not emerge from technical courses alone. They were shaped by the full breadth of my interdisciplinary education, and this essay reflects on how that happened — artifact by artifact, course by course, experience by experience.
Skill One: Network Security & Defense
Artifact 1 — Network Design and Configuration Lab
My first serious encounter with network security came through a lab assignment that required me to design and configure a secure network environment. Before that course, I understood networks abstractly — as systems that connected devices and passed information. The lab forced me to think concretely: Where are the vulnerabilities? How do you segment a network to limit the damage of a breach? What does a properly configured firewall actually look like in practice?
Working through that assignment was difficult in ways I did not anticipate. The technical configuration was challenging, but what surprised me more was how much writing and communication mattered. I had to document every decision I made — why I chose certain configurations, what risks I was mitigating, what I would do differently if the environment changed. That documentation process, which I initially viewed as a formality, turned out to be one of the most valuable parts of the exercise. It forced me to articulate my reasoning, which deepened my understanding of the technical choices themselves. Courses in technical writing and communication, which I had taken as part of my interdisciplinary requirements, turned out to be directly applicable here in ways I had not foreseen (Nakamura & Zlatin, 2020).
Artifact 2 — Secure Network Policy Paper
The second artifact for this skill came from a course that asked me to move beyond configuration and into policy. A network is only as secure as the rules governing its use, and writing a comprehensive network security policy required me to think like an administrator, a risk manager, and a communicator simultaneously. I had to understand not just the technical landscape but the human one — the ways that users interact with systems, the mistakes they make, the behaviors that create vulnerabilities even in well-configured environments.
This assignment drew on my studies in organizational behavior and ethics as much as it drew on my technical knowledge. The National Institute of Standards and Technology (NIST) framework, which I referenced extensively, provided a structure for thinking about security policy that was both rigorous and practical (NIST, 2018). Learning to work within established frameworks — rather than inventing solutions from scratch — was itself an important lesson. It is one that I have seen reinforced in every cybersecurity job advertisement I have reviewed: employers want professionals who understand industry standards, not just individuals who can think independently.
Artifact 3 — Network Breach Case Study
For my third artifact in this skill area, I analyzed a real-world network breach — examining what went wrong, how it could have been prevented, and what the response revealed about the organization’s security posture. This case study approach, which I encountered first in my social sciences coursework, turned out to be a powerful tool for understanding cybersecurity failures. Breaches are rarely purely technical events. They are organizational failures, communication failures, and sometimes policy failures, wrapped in technical packaging.
Writing this case study required me to synthesize information from multiple sources, evaluate competing explanations, and arrive at conclusions that were supported by evidence — skills that my interdisciplinary writing courses had been building all along. The experience confirmed something I now believe deeply: cybersecurity professionals who can only think technically are less effective than those who can also think analytically and communicate clearly (Klein, 2021).
Skill Two: Threat Analysis & Incident Response
Artifact 4 — Threat Analysis Report
Threat analysis is, at its core, an exercise in structured thinking. You are presented with incomplete information and asked to determine what is happening, what might happen next, and what should be done about it. My threat analysis report — which focused on a phishing campaign targeting organizational email systems — required exactly this kind of thinking. I had to move from raw indicators of compromise to a coherent narrative about the threat actor’s likely methods and objectives.
This artifact pushed me to integrate knowledge from my psychology coursework in ways I did not expect. Understanding why phishing works — why humans click on malicious links even when they know better — requires an understanding of cognitive biases, social engineering, and decision-making under uncertainty. The interdisciplinary lens I had developed through my program made me a more complete analyst. A purely technical analysis of a phishing campaign misses half the picture (Workman, 2008).
Artifact 5 — Incident Response Plan
An incident response plan is a document that organizations hope they never have to use — but that they desperately need when something goes wrong. Creating one from scratch was one of the most demanding assignments I completed, not because the technical components were beyond me, but because the document had to be usable by people under stress, in real time, with incomplete information. Clarity, structure, and precision in writing were not optional. They were the point.
My coursework in technical communication directly shaped how I approached this document. I learned to use plain language, logical sequencing, and clear headings — not as stylistic choices, but as functional necessities. The Cybersecurity and Infrastructure Security Agency (CISA) guidelines on incident response provided an important framework that I adapted for the specific organizational context I was working within (CISA, 2021). Reviewing SOC analyst job descriptions while preparing this portfolio, I noticed that incident response planning is listed as a required competency in nearly every posting. This artifact is direct evidence that I can do that work.
Artifact 6 — Cyberattack Case Study
My second case study examined a major ransomware attack, tracing its origins, progression, and organizational impact. This artifact sits at the intersection of technical analysis and policy thinking — understanding not just how the malware behaved, but why the organization was vulnerable, how the response unfolded, and what systemic changes followed. It is the kind of analysis that a SOC analyst must be capable of performing quickly, under pressure, and with high accuracy.
Writing this case study reinforced my understanding of interdisciplinarity as a professional asset. The most complete analyses of cyberattacks draw on computer science, organizational theory, law, and communication. My program gave me exposure to all of these domains, and this artifact reflects that breadth (Rid & Buchanan, 2015).
Skill Three: Ethical Hacking & Penetration Testing
Artifact 7 — CTF Writeup
Capture the Flag competitions were my introduction to offensive security thinking, and they remain some of the most valuable learning experiences I have had. A CTF writeup documents not just what I did, but how I thought — what tools I chose, what approaches I tried, what failed, and what ultimately worked. Writing a clear and thorough writeup after a challenge is itself a skill: it requires me to reconstruct my reasoning and explain it to an audience that was not there with me.
My experience with Kali Linux and Python gave me the technical foundation for CTF participation, but the writing skills I developed through my interdisciplinary coursework made my writeups genuinely useful documents rather than just personal notes. I have learned that in professional penetration testing, the report is often more important than the test itself — because the report is what communicates findings to the people who need to act on them (Engebretson, 2013).
Artifact 8 — Penetration Testing Lab Report
Structured penetration testing follows a professional methodology: scoping, reconnaissance, exploitation, post-exploitation, and reporting. My lab report, produced from a controlled environment using industry-standard tools, walks through each of these phases for a simulated target system. The technical work was engaging and challenging. The reporting work was equally demanding.
This artifact demonstrates something that I believe sets me apart as an emerging professional: I can do the technical work, and I can write about it in a way that non-technical stakeholders can understand. That combination — technical depth plus communication skill — is something that interdisciplinary education builds in ways that purely technical programs often do not. Job advertisements for penetration testers consistently list report writing as a required skill alongside tool proficiency. My portfolio demonstrates both.
Artifact 9 — Nmap Beginner’s Guide (New Artifact)
For my new artifact, I created a practical beginner’s guide to Nmap, one of the most widely used tools in network scanning and penetration testing. This guide was written for an audience of students just beginning their cybersecurity journey — people where I was not long ago. Writing for a beginner audience required me to strip away jargon, build concepts from the ground up, and sequence information in a way that builds understanding progressively.
Creating this artifact was a synthesis of everything my interdisciplinary program taught me about communication, teaching, and technical knowledge. It is also the artifact I am most proud of, because it represents not just what I know, but my ability to share what I know clearly and generously. In a field that sometimes gatekeeps knowledge unnecessarily, I believe that accessible, well-written guides like this one have real value (CompTIA, 2023).
Conclusion
Looking at this portfolio as a whole, I am struck by how thoroughly my interdisciplinary education shaped the professional I am becoming. Cybersecurity is often discussed as a purely technical field, but the evidence in this portfolio tells a different story. Every artifact here required not just technical knowledge, but writing skill, analytical thinking, ethical reasoning, and the ability to communicate across audiences. Those capacities came from courses in writing, social science, ethics, and organizational behavior — not from technical courses alone.
My IDS 300W coursework was particularly foundational. It gave me a framework for thinking about how knowledge is constructed across disciplines and why crossing disciplinary boundaries produces better thinking than staying within any single one (Repko & Szostak, 2017). That framework has made me a better cybersecurity student, and I believe it will make me a better SOC analyst. The threats I will face in that role will not respect disciplinary boundaries. They will be technical, human, organizational, and political all at once. My education has prepared me to meet them on all of those fronts.
I came to this program as a young man from Ghana who loved technology. I leave it as someone who understands that loving technology is not enough — that the most valuable professionals in this field are those who can think broadly, communicate clearly, and act decisively. This portfolio is my evidence that I am becoming that kind of professional.
References
CISA. (2021). Incident response recommendations and best practices. Cybersecurity and Infrastructure Security Agency. https://www.cisa.gov
CompTIA. (2023). Cybersecurity workforce study. CompTIA. https://www.comptia.org
Engebretson, P. (2013). The basics of hacking and penetration testing: Ethical hacking and penetration testing made easy(2nd ed.). Syngress.
Klein, G. (2021). Seeing what others don’t: The remarkable ways we gain insights. PublicAffairs.
Nakamura, L., & Zlatin, M. (2020). Technical communication in cybersecurity contexts. Journal of Technical Writing and Communication, 50(3), 245–268.
NIST. (2018). Framework for improving critical infrastructure cybersecurity (Version 1.1). National Institute of Standards and Technology. https://www.nist.gov/cyberframework
Repko, A. F., & Szostak, R. (2017). Interdisciplinary research: Process and theory (3rd ed.). SAGE Publications.
Rid, T., & Buchanan, B. (2015). Attributing cyber attacks. Journal of Strategic Studies, 38(1–2), 4–37.
Workman, M. (2008). Wisecrackers: A theory-grounded investigation of phishing and pretext social engineering threats to information security. Journal of the American Society for Information Science and Technology, 59(4), 662–674.