UPI Study › Courses › Ethics in Technology › Free lessons › Lesson 7.7 Free with a free account
The Technical Skills and Emerging Trends Shaping Today’s Cybersecurity Workforce
Ethics in Technology · Chapter 7: Hackers, Cyber Warfare, and the Global Battle for Digital SecuritySection 7.7 · lesson 34 of 11617 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of Ethics in Technology.
Lesson complete
Earn the 3 college credits for Ethics in Technology
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: What Database Management Systems Do and Why Protecting Them Is Critical →← How the United Kingdom’s Data Protection Laws Safeguard Personal InformationNext lesson: What Database Management Systems Do and Why Protecting Them Is Critical →
In this lesson
Choosing a security path with evidence, practical work, and realistic expectations.
- Map four families of security work
- Connect technical foundations with communication and judgment
- Compare certification signals and eligibility
- Interpret workforce data and AI, cloud, and zero-trust shifts
Free study notes
Get this lesson's notes by email
The key points and 4 practice questions with answers, in your inbox. One email, free.
One email. Unsubscribe in one click.
Transcript
Everything said in the video, section by section (2,004 words). Read along, or search it.
Chapter 7
Skills, Roles, and a Changing Workforce
Cybersecurity is a collection of different jobs, rather than one activity with a single entry route. An analyst reviews alerts, while a tester writes findings. An engineer builds controls, while an auditor examines evidence. Choosing a path requires understanding that daily work, alongside your strengths and the opportunities available. This lesson maps four families of roles, while recognizing overlap and variation in job titles. We connect networking, systems, scripting, identity, cloud, and logs with practical security decisions. We also examine writing, explanation, collaboration, judgment, ethical restraint, and continuing learning. Then we compare three certifications, separating their signals from requirements and practical capability. The workforce section explains why a staffing-gap estimate is different from advertised vacancies. Finally, we consider artificial intelligence, shared cloud responsibility, and zero-trust access decisions. These shifts create learning needs, without making every applicant's hiring prospects identical. The objective is a realistic plan supported by evidence, rather than a promise that one credential guarantees employment.
Four Families
Security Work Includes Watching, Testing, Building, and Assuring
Defensive work includes monitoring, investigation, containment, threat hunting, and forensic analysis, often called blue-team activity. An analyst may decide which alerts matter, while a responder coordinates action after an incident is confirmed. Offensive work tests defenses under authorization, through penetration testing, research, or red-team exercises. Permission and scope are central, because technical skill does not authorize entering someone else's systems. Build-and-protect work includes engineering, architecture, application security, and cloud security design. Practitioners create and operate controls, making tradeoffs with reliability, cost, and the people using a system. Govern-and-assure work includes governance, risk, compliance, audit, policy, and evidence of obligations being met. These functions help decision-makers understand exposure and demonstrate whether intended controls actually operate. Small organizations may combine several families, while larger ones may divide responsibilities much more narrowly. The groupings therefore support comparison, rather than setting fixed boundaries for every job title. Choose by the actual work, including reports and discussions. A dramatic image alone does not explain the daily responsibilities.
Roles and Entry Paths
A Credible Route Builds the Experience Needed for the Intended Work
Analyst roles can provide an entry route through alert review, triage, escalation, and operational experience. Some include nights or weekends, so the schedule is part of the career decision. Incident response often builds on earlier operational experience, adding containment, investigation, restoration, and reporting. Penetration testing benefits from knowing how systems are built and defended, alongside useful reporting skills. Direct testing entry exists, but a candidate still needs evidence of the relevant depth. Security engineering often connects to systems or network experience, with a strong automation component. Architecture usually carries senior design responsibilities, including arguing for protection amid competing priorities. Governance and compliance analysis offers another route, through obligations, controls, policy, and audit evidence. That work still requires technical understanding, collaboration, and judgment, rather than simply filling in forms. These are tendencies, not universal rules about who can apply or succeed. Compare a real opportunity's duties and support with your demonstrated readiness. A title alone does not establish whether the opportunity fits.
Technical Foundations
Learn Why Systems Behave as They Do, Alongside the Tools Used Today
Networking knowledge helps distinguish unusual traffic from normal communication, including protocol behavior and expected services. Operating-system knowledge explains permissions, processes, services, and controls on systems such as Linux and Windows. Scripting can automate repeatable tasks, but automated results still require validation and safe handling. Identity and access knowledge concerns who can do what, how authentication works, and appropriate privilege. Cloud knowledge adds service-specific responsibilities, distributed resources, and configuration choices that shape exposure. Logging and analysis explain what evidence exists, how to interpret it, and what remains missing. Knowing a tool's interface is useful. Understanding its systems and assumptions is also essential. Tools change, while those foundations help practitioners learn and evaluate unfamiliar technology. For example, an alert makes little sense without understanding the normal behavior it claims to contradict. Similarly, an access rule must be judged against the user's task and the resource's sensitivity. Develop foundations through practice, then connect each tool to the decision or evidence it supports.
Professional Capabilities
A Finding Has Value When People Can Understand and Act on It
A finding needs clear explanation, with evidence people can evaluate. It should support a recommendation that people can act on. Clear writing explains scope, uncertainty, impact, and useful next steps, rather than only technical detail. Nontechnical explanation connects risk to service continuity, cost, safety, and the priorities of decision-makers. Judgment under uncertainty means acting responsibly with incomplete evidence, recording assumptions and points for reassessment. Collaboration matters because a security control can introduce friction into someone else's work. If a process is burdensome, people may quietly work around it while compliance appears satisfactory on paper. Investigate that workflow, explain the concern, and improve the control with the people who use it. Ethical restraint is essential when a role grants privileged access to systems or sensitive information. Respect permission, confidentiality, affected people, and the limits of the task you were authorized to perform. Continuous learning helps maintain competence as systems, threats, requirements, and responsibilities change. These capabilities support effectiveness and advancement, without implying that one weakness permanently determines someone's entire career.
Certification Signals
Preparation, Exam Eligibility, and Full Certification Are Different
Security Plus signals broad preparation across security fundamentals, under CompTIA's vendor-neutral framework. There is no mandatory experience prerequisite, although the issuer recommends networking knowledge and relevant experience. Its recommendation includes about two years of work with a security focus, rather than assuming no preparation. The Certified Ethical Hacker credential concerns offensive-security concepts, techniques, and their authorized use. Official training or an approved experience route supports exam eligibility, while a separate practical assessment exists. The CISSP addresses breadth across eight domains, with experience requirements for full certification. Normally, five years of qualifying experience in at least two domains is required. A qualifying degree or credential can reduce the requirement by one year, under the issuer's conditions. Passing the exam without that experience can lead to Associate status, rather than immediate CISSP designation. Check current issuer requirements, separating recommended preparation, mandatory eligibility, exam success, and full certification. Credentials can support screening and assess knowledge or skills. They cannot guarantee performance in every role or an offer.
Evidence Beyond Credentials
Show Work That Demonstrates Understanding and Responsible Practice
Practical evidence gives an interviewer something concrete to assess, beyond a list of completed exams. A contained laboratory can show how you configured a system, protected it, and interpreted its records. Document the purpose, choices, verification, mistakes, and remaining limitations, rather than presenting only a screenshot. Authorized exercises can demonstrate problem solving, provided you explain the reasoning and respect the environment's rules. A useful contribution to a tool or a clear operational report can show another kind of capability. Adjacent systems, network, support, development, audit, or risk experience may also transfer to security work. Responsible disclosure requires authorization and careful handling, rather than treating a worthy purpose as unlimited permission. An example about finding an overly broad permission should explain the evidence, correction, and subsequent verification. That lets someone ask how you reached the conclusion, and whether the change actually achieved its purpose. Practical work and credentials can complement each other. Their value depends on the role and what they demonstrate. The aim is credible understanding and responsible practice, with evidence suited to the work you want to do.
Workforce Statistics
Additional Staffing Need Is Not a Count of Advertised Vacancies
The widely repeated four-point-eight-million staffing gap comes from a dated twenty twenty-four study. The same study estimated an active global workforce of roughly five point five million people. The gap estimated additional staffing need through its method and respondents' reported organizational needs. It did not count four point eight million advertised, funded vacancies awaiting any qualified applicant. Job postings are a different measure, requiring their own geography, time period, and treatment of duplicates. A global need estimate should not be compared with one country's postings as if their populations match. Nor was the same four-point-eight-million number a stable estimate throughout an entire decade. In twenty twenty-five, the publisher omitted a gap estimate, emphasizing specific skills needs instead. The stated reason concerned participants prioritizing skills over simply adding headcount, rather than proof that all staffing needs disappeared. Training claims and headlines can simplify such statistics, so check the original definition and method. Need and funded opportunities remain different measures, with separate evidence. A career decision also requires assessing capabilities and readiness.
2025 Survey Findings
Skills Needs and Budget Pressure Can Coexist
The twenty twenty-five survey included more than sixteen thousand practitioners and decision-makers, across several world regions. Ninety-five percent reported at least one cybersecurity skills need within their organization. Fifty-nine percent described critical or significant needs, compared with forty-four percent in the previous year's study. Seventy-two percent agreed that staff reductions significantly increase breach risk, expressing a view rather than a measured causal effect. Thirty-six percent reported budget cuts, while twenty-four percent reported cybersecurity layoffs. These pressures remained broadly level, rather than disappearing because skills needs were high. The figures describe participating respondents, not a census of every employer or a forecast for each applicant. Need and budget constraints can coexist, so an organization may lack skills without funding an immediate additional position. That supports building specific capabilities and reading actual requirements, rather than assuming indiscriminate hiring. It also supports attention to training and retaining existing staff, alongside possible recruitment. For a newcomer, the implication is realistic preparation and evidence, not either guaranteed employment or inevitable exclusion.
Artificial Intelligence
Using AI for Defense Differs From Protecting AI Systems
Artificial intelligence affects security in three related but distinct ways, starting with assistance for defenders. It can help summarize activity, draft queries, triage information, and propose steps for an analyst to check. The useful goal is handling volume, while preserving verification, confidentiality, and responsibility for decisions. Attackers can also use more fluent deception and convincing impersonation, making poor wording an unreliable warning sign. Those capabilities can improve scale and credibility, without making every generated message accurate or every attack successful. The third concern is protecting the artificial-intelligence systems themselves, including models, data, and integrations. Risks include corrupted data, manipulated instructions, and disclosure of information that should remain restricted. Defensive assessment must consider access boundaries, provenance, monitoring, and the role the system plays in decisions. Using a model to assist analysis is therefore different from securing that model against misuse. Machine-generated confidence does not establish correctness, so practitioners need to evaluate evidence and limitations. Ask how the technology helps, how adversaries misuse it, and what additional assets its adoption creates.
Cloud and Zero Trust
Responsibilities and Access Decisions Depend on the Actual Service and Request
Cloud security divides responsibilities between a provider and its customer, according to the actual service. Providers protect underlying infrastructure, while customers retain responsibilities for information, identities, configurations, and deployed workloads. The precise division varies, so read the service model rather than assuming every layer belongs to one party. Infrastructure defined in code can replicate a mistaken setting rapidly, or consistently enforce a secure baseline. Reviewing, testing, and monitoring configuration at scale therefore becomes an important practical capability. Zero trust removes implicit trust based solely on network location or asset ownership. Access decisions consider identity, device condition, the requested resource, and relevant context, with limited privileges. Device posture can include patching, encryption, and management status, according to the policy and available evidence. Reassessment, segmentation, and detailed records support the approach, rather than trusting broad access after one boundary check. Identity becomes central, without eliminating the importance of network controls or every other discipline. Zero trust is an architectural approach, rather than simply a stronger perimeter or a product that guarantees security.
Worked Career Decision
Choose an Entry Route, Build Evidence, and Revisit the Plan
For the worked decision, begin with the daily activity you want to pursue and your existing strengths. Compare investigation, authorized testing, building systems, and governance, rather than choosing only a fashionable title. Identify gaps in relevant foundations and communication, then select a permitted project that addresses them. Explain its evidence and limitations, and seek feedback from people familiar with the work. Compare real opportunities with your readiness, including adjacent roles and the support available for learning. A student seeking penetration testing can keep that goal, while building system knowledge and useful reporting ability. Analyst, engineering, or adjacent technical work may provide a route, while direct entry can fit some opportunities. Choose a credential for the capabilities and requirements it supports, rather than accumulating titles without a purpose. Remember that a staffing-need estimate does not count vacancies, and a survey percentage does not predict your outcome. Revisit the plan as you learn, gain evidence, and understand AI, cloud, and access decisions more deeply. The strongest conclusion is a defensible next step, supported by realistic requirements and responsible practical work.
About Ethics in Technology at UPI Study
Ethics in Technology (Computer Science 195) is a self-paced online course of 116 video lessons in 15 chapters, from cybersecurity basics, privacy and surveillance to big data, hacking, malware, network defense, intellectual property, cybercrime, encryption, emerging technology and digital citizenship. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Computer Science courses
Compare: Cybersecurity vs Ethics in Technology · Which ethics course?
Why take it here
Why students take Ethics in Technology with UPI Study
Where the credit goes
Universities that work with NCCRS
Ethics in Technology carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About The Technical Skills and Emerging Trends Shaping Today’s Cybersecurity Workforce
What are the main career paths in cybersecurity?
What technical and soft skills does a cybersecurity job require?
What is the difference between Security+, CEH and CISSP?
Is there really a shortage of 4.8 million cybersecurity workers?
About the Ethics in Technology course
How many college credits is Ethics in Technology?
How much does Ethics in Technology cost and what is included?
Which universities accept UPI Study credits?
How long does Ethics in Technology take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in Ethics in Technology.
116 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →