CYBERTM

 

REPORT

 

Course Introduction: CYBERTM

I am starting my journey in the CyberTM course. This course is about understanding technology, management, and security in the digital world. I see it as a foundation for learning how to think critically about cyber systems and their risks. In this report, I will share what the course means to me, what I expect to learn, and how I will apply it in my work and daily life.

The first part of the course helps me build a clear picture of cyber technology. I learn that technology is more than just computers. It includes networks, cloud systems, mobile devices, and even artificial intelligence. By learning these basics, I can better understand how digital systems work together. Simple examples, like how my phone connects to Wi-Fi, make the big picture easier for me to grasp.

The second part focuses on threats. I realize that every system has weaknesses. Hackers try to use these weaknesses to steal data or cause damage. In this course, I will study real examples of attacks and how they were stopped. I want to see not just the problems but also the solutions. This helps me prepare for real-life situations where I may need to act quickly.

Management is another key part of CyberTM. I learn that cyber security is not only about technology but also about people and processes. A company needs rules, policies, and training for its employees. If people are careless, even the best system can fail. I want to practice making policies that are simple and effective, because I believe clear rules help everyone stay safe online.

In the course, I also learn about risk management. I need to identify what is most important to protect. For example, in a hospital, patient data is more valuable than simple office files. By ranking risks, I can choose where to spend time and money. This logical way of thinking makes security more practical and realistic.

The CyberTM course also teaches me about laws and ethics. I understand that technology is powerful, but it must be used responsibly. I learn about privacy, data rights, and global regulations. These lessons remind me that cyber work is not just technical—it is also moral. I want to follow ethical practices so that I respect the trust people place in technology.

Another benefit of this course is teamwork. Cyber problems are too big for one person to solve alone. In practice, I must work with managers, engineers, and users. Through group projects, I learn how to explain technical ideas in simple words. This skill helps me as a leader and a teacher, because I can guide others without making them feel lost.

At the end of the course, I expect to have a strong base in cyber knowledge. I will know the main threats, the tools to defend against them, and the ways to manage teams and policies. I believe this knowledge will help me as a performer, teacher, and composer who also lives in the digital world. Technology is part of my daily life, and I want to use it safely and wisely.

In conclusion, the CyberTM course gives me a full introduction to technology, threats, management, risk, and ethics. I write this report in simple sentences to show what I have learned and what I hope to achieve. This course is not only about machines; it is about people, ideas, and responsibility. I feel ready to continue this journey.

 

 

 

 

 

 

 

 

 

Module 1: Governance and Compliance

In this module, I begin to see how governance and compliance shape the world of cyber security. For me, this topic is about rules, responsibilities, and accountability. It shows me that technology does not exist alone. It is guided by laws, policies, and standards that protect people and organizations. I want to explain what I have learned in simple sentences and in my own words.

Governance means leadership and control. It is the way an organization makes decisions about security. I learn that leaders must create policies, assign roles, and make sure systems are safe. Governance is not just technical. It is also about vision and planning. I see it as a road map that helps me and others know what to do.

Compliance means following rules. These rules come from laws, government agencies, or industry standards. For example, in healthcare, patient data must follow privacy laws. In finance, companies must follow strict rules for transactions. I learn that compliance protects trust. When rules are followed, people feel safe giving their information.

This module teaches me that governance and compliance work together. Governance creates the plan, and compliance makes sure the plan is followed. If one is missing, the system becomes weak. I think of it like music: governance is the score, and compliance is the performance. Both are needed to create harmony.

I also study frameworks. These are guides that organizations use for security. Examples are ISO standards and NIST frameworks. They give clear steps for managing risk and building strong systems. I like how frameworks provide structure, just like scales and études do in music. They give me a foundation to build on.

Policies are another key idea in this module. A policy is a written rule that explains what is allowed and what is not. For example, a password policy may say that passwords must be strong and changed every 90 days. I learn that policies must be clear, simple, and fair. If rules are confusing, people will not follow them.

Risk management is also part of governance. Leaders must decide what risks are acceptable and which must be reduced. I learn that not all risks can be removed, but they can be managed. This way, resources are used wisely. I see this as a practical balance between safety and cost.

This module also highlights accountability. Every person in an organization has a role. From leaders to staff, everyone must follow rules and report problems. I realize that culture is important. A culture of compliance makes people proud to do the right thing.

Ethics connects closely with compliance. Following the law is required, but acting ethically goes further. It means respecting privacy, being honest, and protecting users even when no one is watching. I believe this is the heart of cyber responsibility.

At the end of this module, I feel that governance and compliance give me a strong base for my cyber journey. They remind me that cyber security is not only technical. It is also legal, organizational, and ethical. As a teacher and performer, I can apply these lessons to my own studio and digital work. I must set rules, follow them, and guide others to do the same.

In conclusion, Module 1 shows me that governance and compliance are about leadership, rules, and trust. They help protect information and people. They guide actions, reduce risks, and build strong systems. I now see governance and compliance as the pillars that hold the world of cyber security together.

 

 

 

 

 

 

 

Module 2: Network Security Testing

In this module, I learn about network security testing. This topic shows me how to check if a network is safe. I understand that networks connect computers, devices, and servers. If the network is weak, hackers can break in. Testing helps me find problems before attackers do.

First, I learn that testing is like a health check. Just as a doctor checks a patient, I must check the network. I look at firewalls, routers, and access points. These are the gates of the network. If a gate is weak, it can be an entry for attackers. By testing, I make sure the gates are strong.

There are different kinds of testing. One type is vulnerability scanning. In this test, I use tools to find weaknesses in the system. The tool shows me open ports, weak passwords, or old software. This gives me a list of problems that must be fixed. I like that scanning is fast and automatic, but I know it does not solve the problem—it only shows where the problem is.

Another type is penetration testing. Here, I act like a hacker. I try to break into the system, but I do it in a safe way. This test shows me how much damage an attacker could do. I learn that penetration testing takes skill, planning, and permission. I must respect laws and ethics when I do it.

I also learn about security audits. This is when I check if the network follows policies and rules. An audit may ask: Are updates installed? Are users following password rules? Are backups stored safely? Audits make sure the organization is not only secure but also compliant with standards.

Testing also includes monitoring. I use tools that watch network traffic. These tools can show me if strange activity is happening. For example, if a computer is sending data to an unknown place, that could mean an attack. By monitoring, I can stop problems before they grow.

This module teaches me about risk. Not every problem is equally dangerous. Some weaknesses are small, while others could cause major harm. I learn to rank problems by risk level. This helps me decide what to fix first. It is like tuning a violin: I must focus on the string that is most out of tune before I can play well.

Documentation is also important. When I finish a test, I must write a clear report. The report explains what I found, how serious it is, and how to fix it. Good reports help leaders make decisions. Without documentation, the test has no value.

Another lesson in this module is teamwork. Network testing is not done by one person alone. I must work with IT staff, managers, and even users. Everyone must understand their role. Clear communication is key, especially when I explain complex issues in simple words.

At the end of this module, I see that network security testing is both technical and practical. It is not just about tools; it is about process, people, and responsibility. By testing, I protect data, users, and organizations. I feel more confident knowing that I can find weaknesses before attackers do.

In conclusion, Module 2 teaches me how to test networks for safety. I learn about scanning, penetration testing, audits, monitoring, risk, and reporting. These skills give me the power to protect systems and build trust. Network security testing shows me that prevention is better than cure, and I am ready to apply these lessons in real life.

 

 

 

 

 

 

 

 

Module 3: Threat Intelligence

In this module, I learn about threat intelligence. Threat intelligence means collecting and studying information about cyber threats. I see it as a way to stay one step ahead of attackers. Instead of waiting for an attack to happen, I learn to predict, prepare, and respond.

The first idea I learn is that threats are always changing. Hackers create new tools, malware, and tricks every day. If I only rely on old defenses, I will fail. Threat intelligence gives me updated knowledge. It tells me who the attackers are, what methods they use, and what targets they want. This helps me prepare my defenses.

I also learn that threat intelligence comes in different forms. One type is strategic intelligence. This is big-picture knowledge. It explains why certain groups attack and what their goals are. For example, a nation-state might attack for political reasons, while a criminal group wants money. Knowing this helps leaders make smart decisions.

Another type is tactical intelligence. This focuses on the methods attackers use. I learn about phishing, ransomware, and denial-of-service attacks. Tactical intelligence shows me the patterns, tools, and techniques of attackers. It helps me set up firewalls, filters, and alerts in the right way.

I also study operational intelligence. This type is about current and specific threats. For example, if there is a new malware spreading today, operational intelligence tells me how it works and how to block it. This type requires fast action. I must act quickly to stop the attack before it spreads.

Finally, there is technical intelligence. This gives me details like IP addresses, domain names, or file hashes used by attackers. These details are very specific. I can use them in my monitoring systems to detect and block attacks.

This module shows me how threat intelligence is collected. Some sources are open, like news reports, blogs, and public databases. Others are private, like paid intelligence feeds or government reports. I also learn about information-sharing groups where organizations work together. Sharing data makes everyone stronger because one company’s experience can protect many others.

I learn that analysis is the key to threat intelligence. Collecting data is not enough. I must filter, organize, and understand it. I must ask questions: Is this information true? Is it useful for me? How urgent is it? Without analysis, data becomes noise. With analysis, data becomes knowledge.

This module also teaches me about reporting. A good intelligence report is clear, simple, and useful. Leaders want short and direct answers. They want to know the risk, the impact, and the action needed. As a student, I practice writing in a way that non-technical people can understand.

Ethics is also important. I must follow laws when I collect and share intelligence. I cannot spy on people without reason. I cannot use the knowledge for harm. Threat intelligence must always be used to protect, not to attack.

At the end of this module, I feel more prepared. I understand that threat intelligence is about being proactive. It helps me see the enemy before they strike. It helps me protect my work, my students, and my community. Just as a musician studies the score before performing, I must study threats before they appear.

In conclusion, Module 3 teaches me that threat intelligence is about knowledge, prediction, and action. It includes strategic, tactical, operational, and technical levels. It relies on data collection, analysis, sharing, and reporting. Most of all, it is about staying ready. Threat intelligence gives me the vision to face the cyber world with confidence.

 

 

 

 

 

 

 

 

Module 4: Endpoint Vulnerability Assessment

In this module, I learn about endpoint vulnerability assessment. An endpoint is any device that connects to a network. This includes laptops, desktops, tablets, and mobile phones. Servers and printers can also be endpoints. I see that every endpoint is a possible door into the system. If one door is weak, attackers can use it to enter.

The goal of endpoint vulnerability assessment is to find weaknesses before attackers do. I learn that no system is perfect. Every device has flaws in software, hardware, or configuration. By testing and scanning endpoints, I can find these flaws. Once I know the problems, I can fix them or reduce the risk.

The first step in assessment is identification. I must know all the endpoints in the network. If I miss one, that device could be an easy target. I use tools to discover all connected devices. This step reminds me of tuning all strings on a violin. If one string is ignored, the performance will suffer.

The second step is scanning. I use vulnerability scanners to check endpoints. These tools look for missing updates, weak passwords, or unsafe settings. For example, if a laptop still runs old software, it could be open to attack. Scanners save time by giving me a list of issues.

The third step is analysis. Not every weakness is equally dangerous. Some may have little impact, while others could allow full control of the device. I learn to rank vulnerabilities by risk. This helps me decide what to fix first. It is like practicing music: I must focus on the hardest parts before the easy ones.

The fourth step is remediation. This means fixing the problems. Sometimes it is simple, like updating software or changing a password. Other times it is harder, like reconfiguring a system or replacing hardware. Remediation is the action that makes endpoints stronger.

I also learn about patch management. Patches are updates that repair flaws in software. Without patches, old weaknesses remain open. I must create a schedule for installing patches. I also need to test patches first, to make sure they do not break other systems.

Another lesson is continuous assessment. One test is not enough. New vulnerabilities appear all the time. Attackers are always looking for new ways in. I must test regularly, update tools, and stay alert. Security is an ongoing process, not a one-time task.

This module also covers reporting. After an assessment, I must write a clear report. The report shows what was found, how serious it is, and what actions are needed. Good reporting helps managers and teams understand the risks. It also proves compliance with laws and standards.

Ethics and responsibility are part of this process. I must use my knowledge for defense only. I must not expose or misuse the information I find. Trust is very important. If people trust me, they will let me test their systems and keep them safe.

At the end of this module, I see endpoint vulnerability assessment as a key skill. It helps me protect every device that connects to a network. I learn how to identify, scan, analyze, and fix weaknesses. I also see the value of patches, continuous testing, and good reporting.

In conclusion, Module 4 shows me that endpoints are both valuable and vulnerable. They are the front lines of cyber defense. By assessing them carefully, I make the whole network stronger. This knowledge gives me confidence to protect my work and the people I serve.

 

 

 

 

 

 

Module 5: Risk Management and Security Controls

In this module, I learn about risk management and security controls. I see that every system has risks. A risk is the chance that something bad will happen. In cyber security, risks can be data loss, system failure, or an attack. My goal is not to remove all risks, but to manage them in a smart way.

The first step is identifying risks. I must look at the system and ask what could go wrong. For example, weak passwords, missing updates, or careless users can all create risks. This step is like reading a music score carefully before I play. If I do not notice the difficult passages, I will fail in performance.

The second step is assessing risks. Not all risks are equal. Some are small and cause little harm, while others are big and could destroy the system. I learn to measure risks by two things: how likely they are to happen, and how serious the damage would be. High-likelihood and high-impact risks must be addressed first.

The third step is prioritizing risks. Since resources are limited, I cannot fix everything at once. I must choose the most important risks to deal with. This step helps me focus on what matters most.

The fourth step is treating risks. There are four main choices: avoid, reduce, transfer, or accept. Avoiding a risk means not doing the activity that causes it. Reducing a risk means adding controls, like stronger passwords. Transferring a risk means giving it to someone else, like buying cyber insurance. Accepting a risk means living with it if it is small and not worth fixing.

Next, I learn about security controls. These are the defenses I use to reduce risks. There are three main types: preventive, detective, and corrective. Preventive controls stop attacks before they happen, like firewalls or encryption. Detective controls find problems when they occur, like monitoring tools and alerts. Corrective controls fix damage after an attack, like backups or recovery plans.

I also learn about administrative controls. These are rules and policies. For example, requiring employees to change passwords every 90 days is an administrative control. Technical controls use technology, like antivirus software. Physical controls protect buildings and devices, like locks or cameras. Together, these controls create layers of defense.

Another lesson in this module is continuous improvement. Risk management is not a one-time project. Threats change, systems change, and people change. I must review risks regularly and update controls. This is like practicing music daily to stay sharp and ready.

Reporting is also important. I must explain risks and controls to managers in simple words. They need to understand what the risks are, what actions are being taken, and what support is required. Good communication builds trust and teamwork.

Ethics is part of risk management too. I must use my skills honestly and responsibly. If I hide risks or misuse controls, I break trust. My role is to protect people, data, and systems, not to create fear or confusion.

At the end of this module, I feel stronger as a cyber learner. I now understand how to find, assess, and treat risks. I also know how to use security controls to reduce harm and build defense. This knowledge makes me ready to handle real-world problems with clarity.

In conclusion, Module 5 teaches me that risk management and security controls are about balance. I cannot remove all risks, but I can manage them wisely. With planning, controls, and honesty, I can protect systems and people. This module gives me confidence to act as a responsible guide in cyber security.

 

 

 

 

 

 

 

Checkpoint Exam: Vulnerability Assessment and Risk Management

As I prepare for the checkpoint exam on vulnerability assessment and risk management, I think about what I have learned in Modules 4 and 5. These topics are connected because vulnerabilities create risks, and risk management helps me decide how to deal with them. The exam will test my ability to explain the process clearly and apply it to real-world problems.

The first step in vulnerability assessment is identification. I must find all the endpoints and systems in a network. Endpoints include laptops, desktops, mobile devices, servers, and printers. If I miss even one, that device can become an easy way for attackers to enter. The exam may ask me to explain why identification is the foundation of assessment.

The second step is scanning. I use tools to scan systems for weaknesses. These tools look for missing patches, weak passwords, old software, or unsafe configurations. Scanning gives me a list of problems. I know the exam may ask me to describe the difference between automatic scanning and manual testing.

The third step is analysis. Not all weaknesses are equally dangerous. Some flaws may only cause small problems, while others could allow full control of a system. I must rank vulnerabilities by severity. High-risk flaws are fixed first. I think the exam will ask me to explain how to measure risk based on likelihood and impact.

The fourth step is remediation. This is the action I take to fix or reduce weaknesses. It can mean applying patches, changing passwords, or reconfiguring systems. Sometimes it is harder, like replacing old hardware. Remediation is important because finding vulnerabilities means nothing if I do not act on them.

The fifth part is reporting. I must write a clear report about what I found, how serious it is, and what actions should be taken. The exam may test my ability to explain why reporting is necessary for both technical teams and managers.

Risk management connects directly to vulnerability assessment. When I find weaknesses, I must decide what to do with the risks they create. I learned about the four main options: avoid, reduce, transfer, or accept. Avoiding a risk means not doing the activity at all. Reducing a risk means adding controls, like firewalls. Transferring a risk means using insurance or outsourcing. Accepting a risk means living with it if it is small. I believe the exam will ask me to apply these options to examples.

I also studied security controls. Preventive controls stop problems before they happen, like encryption. Detective controls find problems when they occur, like intrusion detection systems. Corrective controls fix damage after a problem, like backups. Controls can also be administrative, technical, or physical. I think the exam will ask me to match risks with the right type of control.

Another key lesson is continuous improvement. Vulnerabilities change, and new risks appear. Assessment and risk management must be ongoing. The exam may ask me to explain why one-time testing is not enough.

In conclusion, the checkpoint exam on vulnerability assessment and risk management will test my ability to identify, scan, analyze, remediate, and report weaknesses. It will also test how I use risk treatments and security controls. I feel ready because I understand that finding weaknesses is only the first step, and managing risks wisely is what makes systems safe.

 

 

 

 

 

 

 

 

 

Module 6: Digital Forensics and Incident Analysis and Response

In this module, I learn about digital forensics and incident analysis and response. I understand that cyber incidents will happen, no matter how strong the defenses are. The key is how I respond. This module shows me how to investigate, analyze, and recover when something goes wrong.

The first part is digital forensics. This is the science of collecting and studying digital evidence. I learn that evidence can be files, logs, emails, or network records. The goal is to find out what happened, who did it, and how it was done. I must follow rules so the evidence can be trusted in court or in a report.

The second part is incident analysis. An incident is any event that harms or threatens the system. It could be a virus, a phishing attack, or stolen data. When an incident happens, I must study it carefully. I ask questions: What was the entry point? What data was touched? How did the attack spread? This analysis helps me understand the scale of the problem.

The third part is incident response. This is the process of dealing with the incident. I learn about the response cycle. The first step is preparation. Before an incident happens, I must have plans, tools, and trained staff ready. The second step is detection. I need to know when an incident starts, using alerts and monitoring tools. The third step is containment. I stop the attack from spreading, like isolating infected devices.

The fourth step is eradication. Here, I remove the cause of the attack. This could mean deleting malware, closing a hole in the system, or changing stolen passwords. The fifth step is recovery. I bring the system back to normal. I may restore data from backups or rebuild servers. The last step is lessons learned. I write a report, share knowledge, and update defenses so the same problem does not happen again.

This module also teaches me about the importance of chain of custody. When I collect evidence, I must record who handled it, when, and how. If I do not, the evidence could be rejected or questioned. I see that trust and accuracy are vital in forensics.

Another lesson is teamwork. Incident response is not done alone. It involves IT staff, managers, lawyers, and sometimes law enforcement. I must communicate clearly and work together. Everyone has a role, and good coordination makes the response faster and stronger.

I also learn about tools. Forensics tools help me recover deleted files, track user activity, and scan memory. Incident response tools help me monitor networks and block attacks. I see that technology supports me, but I must use it with skill and responsibility.

Ethics is very important in this module. I must handle evidence with respect. I cannot change, leak, or misuse what I find. Victims must be treated with care. The goal is always to protect, not to punish unfairly.

At the end of this module, I feel prepared to face real incidents. I understand the steps of forensics and response. I know how to collect evidence, analyze events, contain attacks, and recover systems. I also value the role of lessons learned, because each incident can make the system stronger.

In conclusion, Module 6 teaches me that digital forensics and incident analysis and response are about preparation, action, and learning. I see that incidents are not just problems—they are also chances to improve. This knowledge gives me confidence to respond calmly and wisely when a crisis comes.

 

 

 

 

 

 

 

 

Checkpoint Exam: Incident Response

As I prepare for the checkpoint exam on incident response, I think about the lessons I have learned in Module 6 and the earlier modules. Incident response is one of the most important parts of cyber security. It is the process I follow when an attack or a problem happens. I know that the exam will test my ability to explain the steps clearly and apply them to real situations.

The first idea is preparation. Before an incident happens, I must be ready. This means having an incident response plan, trained staff, and the right tools. Preparation is like practicing music before a concert. If I practice well, I am ready when the time comes. In the exam, I may be asked how preparation reduces damage.

The second step is detection. This is how I discover that something is wrong. I can use monitoring tools, intrusion detection systems, or reports from users. Quick detection is important because the faster I see the problem, the faster I can respond. I expect the exam will ask me to explain how to detect suspicious activity on a network.

The third step is containment. This means stopping the attack from spreading. For example, if a computer is infected, I can disconnect it from the network. Containment buys me time to study the problem. The exam may ask me to describe short-term containment (quick action) and long-term containment (more stable solutions).

The fourth step is eradication. At this stage, I remove the cause of the attack. This may include deleting malware, disabling accounts, or patching software. Eradication is like cleaning the violin strings before playing. If I leave dirt, the sound is weak. If I leave malware, the system is weak. I believe the exam will test my ability to explain why eradication is necessary after containment.

The fifth step is recovery. This is when I restore the system to normal. I may reload backups, reinstall systems, or check that everything works again. Recovery also means monitoring the system to be sure the attack does not return. The exam may ask me to describe how to make recovery safe and effective.

The sixth step is lessons learned. This is the final part of incident response. I write a report, study what went wrong, and improve defenses. The goal is not only to fix the problem but also to prevent it from happening again. In the exam, I may need to explain how lessons learned help an organization grow stronger.

I also know the exam may test me on digital forensics. This means collecting and analyzing evidence. I must protect the chain of custody so that evidence can be trusted. I may be asked to explain how evidence supports both investigation and prevention.

Teamwork is another theme. Incident response is not done alone. I must work with IT staff, managers, and sometimes law enforcement. Communication is key. The exam may ask how I would explain a technical problem in simple words to a manager.

In conclusion, the checkpoint exam on incident response will test my knowledge of preparation, detection, containment, eradication, recovery, and lessons learned. It will also test my skills in forensics, teamwork, and communication. I feel ready because I can explain the steps in simple words and connect them to real actions. Passing this exam will prove that I can respond calmly and effectively when a cyber incident happens.

 

 

 

 

 

 

 

 

 

 

Cyber TM – Final Exam

As I prepare for the Cyber TM final exam, I reflect on everything I have learned in this course. The exam is not just a test of memory. It is a test of my understanding of technology, threats, governance, compliance, risk management, and incident response. I see this exam as the moment where all the modules connect.

The first thing I remind myself is the importance of governance and compliance. I learned that organizations need leadership, rules, and policies. Governance provides the direction, and compliance ensures the rules are followed. I expect the exam will ask me about frameworks, policies, and laws. I know I must explain how governance builds trust and compliance protects people.

The second area is network security testing. I studied how to scan, audit, and monitor networks. I learned about vulnerability scanning, penetration testing, and audits. These skills help me find weaknesses before attackers do. For the exam, I must be ready to describe the difference between scanning and penetration testing, and explain why documentation is important.

The third area is threat intelligence. I learned about the four levels: strategic, tactical, operational, and technical. Each level gives different kinds of information. Strategic intelligence looks at big goals, tactical focuses on methods, operational is about active threats, and technical gives specific details like IP addresses. I think the exam will test my ability to explain each type and how they work together.

The fourth area is endpoint vulnerability assessment. I learned that every device on a network is a possible weak point. The exam may ask me to describe how I identify, scan, analyze, and remediate vulnerabilities. I also know patch management is important. Keeping systems updated is one of the best defenses.

The fifth area is risk management and security controls. I studied how to identify, assess, and treat risks. I remember the four choices: avoid, reduce, transfer, or accept. I also learned about controls—preventive, detective, corrective, administrative, technical, and physical. The exam may test me on applying these choices to real-world examples.

The sixth area is digital forensics and incident analysis and response. I practiced the six steps: preparation, detection, containment, eradication, recovery, and lessons learned. I also learned about evidence collection and chain of custody. The exam may ask me to explain how I would handle an incident from start to finish.

The final exam also checks my critical thinking. I must not only repeat facts but also connect ideas. For example, I may be asked how governance connects with incident response, or how risk management connects with endpoint assessments. These questions test my ability to see the big picture.

I prepare by reviewing notes, practicing definitions, and writing short answers. I also think about how I would explain these ideas to someone else. If I can explain clearly, then I know I understand.

At the end of this course, I feel proud of my progress. I started with simple knowledge of technology, but now I see the full landscape of cyber security management. The final exam is my chance to show that I can apply this knowledge with confidence.

In conclusion, the Cyber TM final exam is more than a test. It is proof that I can connect governance, testing, intelligence, assessment, risk, and forensics into one clear framework. Passing the exam means I am ready to face the real challenges of cyber security with skill and responsibility.

 

 

 

 

 

 

 

 

 

 

Q&A Report

Q1: How do I evaluate security controls according to ethical, regulatory, and legal compliance requirements?
A1: I start by reviewing the rules that apply to my organization. These rules can come from laws, industry standards, or internal policies. I check if the security controls, like firewalls or encryption, meet those rules. I also make sure they respect ethical principles, such as protecting user privacy. I document every step so I can show proof of compliance during audits. If a control is weak or missing, I recommend changes.

Q2: How do I use tools for network security testing?
A2: I use testing tools to check if the network is safe. Tools like vulnerability scanners, penetration testing software, and packet sniffers help me find problems. I run tests on servers, routers, and switches to see if attackers could enter. I also simulate attacks to check if defenses work. After testing, I create a report with results and suggest fixes. This helps me improve the security of the network step by step.

Q3: How do I evaluate threat intelligence sources?
A3: I first look at where the intelligence comes from. Reliable sources include government agencies, trusted security vendors, and information-sharing groups. I check if the data is recent and relevant. If a source provides outdated or vague alerts, I may not trust it. I also compare different sources to confirm accuracy. When I use good intelligence, I can predict attacks and protect systems before damage happens.

Q4: How are endpoint vulnerabilities assessed and managed?
A4: Endpoints are devices like laptops, desktops, and mobile phones. I assess them by running vulnerability scans to find outdated software, weak passwords, or missing patches. Once I find problems, I manage them by applying updates, using antivirus tools, and enforcing strong authentication. I also train users to avoid unsafe practices, like clicking on unknown links. I keep records of all vulnerabilities and make sure they are fixed quickly.

Q5: How do I select security controls based on risk assessment outcomes?
A5: I first conduct a risk assessment to identify threats, vulnerabilities, and impacts. If a system stores sensitive data, I apply stronger controls, like encryption and strict access rules. If the risk is low, I may use lighter controls. My goal is to balance cost, usability, and security. I choose the best control for each risk scenario. This ensures resources are used wisely and risks are reduced.

Q6: How do I use incident response models and forensic techniques to investigate security incidents?
A6: When an incident happens, I follow a response model such as NIST or SANS. I begin by identifying the incident, containing it, and then eradicating the cause. I collect logs, memory dumps, and system images as evidence. I use forensic tools to analyze what happened and how. I report my findings clearly so future incidents can be prevented. I also update security policies and train staff based on lessons learned.

 

 

 

 

 

 

 

 

 

 

Q&A Report

Q1: How can I add devices and connect them via cables or wireless?
A1: I can add devices to my network by choosing them from a device list. These devices may be computers, routers, switches, or printers. Once I place them in the network space, I connect them. If I use cables, I select the right cable type and attach it to the correct ports. If I want wireless, I connect devices through Wi-Fi settings. I make sure each device has the correct configuration, such as IP addresses. This way, I can build a working network that lets devices talk to each other.

Q2: How can I select, delete, inspect, label, and group components within my network?
A2: I can select components by clicking on them in the network view. If I no longer need a component, I delete it. I can inspect a device by checking its settings, status, and logs. This helps me see if the device is working correctly. I can also label components to give them names. This makes it easy to recognize each part of the network. If I want better organization, I group components. For example, I may group all servers together or all wireless devices in one cluster. These actions help me manage and understand my network more clearly.

Q3: How can I manage my network by opening an existing or sample network?
A3: I can open an existing network file that I have saved before. This lets me continue working where I left off. If I want to learn or practice, I can open a sample network. A sample network shows me pre-built devices and connections. I can study how it works and make changes to learn. This helps me improve my skills in network design and troubleshooting.

Q4: How can I save my current network?
A4: When I build or change a network, I can save it as a file. This keeps all my devices, cables, and settings in place. Later, I can open the file and continue working. Saving is very important because it protects me from losing my work. I often save my progress to avoid starting over if something goes wrong.

Q5: How can I modify my user profile or preferences?
A5: I can open the settings menu to update my profile. In the profile, I may add my name, email, or other information. I can also adjust preferences. These preferences may include display settings, default devices, or performance options. By changing preferences, I make the network tool work in the way that fits me best. This helps me feel more comfortable and efficient while managing networks.

 

Summary

I can manage a network by adding devices, connecting them with cables or wireless, and organizing components. I can select, delete, inspect, label, and group devices to make the network clear. I can open existing or sample networks to continue or practice. Saving my current network ensures I do not lose progress. Finally, I can adjust my profile and preferences to work better. These steps give me control and flexibility in building and maintaining networks.

 

 

 

 

 

 

 

 

 

 

CISCO

I want to explain what I know about Cisco. Cisco is a global technology company. It makes networking hardware, software, and services. I think of Cisco as a leader in building the backbone of the internet. When I hear the name Cisco, I think about routers, switches, and security tools. These devices help computers and networks connect to each other.

I use simple words to describe Cisco’s role. Cisco builds equipment that lets information travel across the world. If I send an email, browse the web, or watch a video, the data often moves through Cisco devices. This makes Cisco very important in daily life, even if I do not always see it directly. Cisco is like the hidden infrastructure of communication.

Cisco is known for its routers and switches. A router is a device that connects networks together. A switch is a device that connects many computers inside the same network. I imagine a router as a road junction and a switch as a local street. They both manage traffic, but on different levels. Cisco produces both, and they are widely used in businesses and organizations.

Security is also a major focus for Cisco. The internet is full of risks. Hackers and cyber threats try to break into networks. Cisco develops firewalls, intrusion detection systems, and security platforms. I see these tools as shields that protect data. Cisco wants to make sure information moves safely from one place to another.

Cisco also works with cloud technology. Many companies use cloud computing to store data and run applications. Cisco provides solutions to connect private networks with cloud services. This helps businesses work faster and more flexibly. I think of it as a bridge between traditional IT and modern cloud systems.

Cisco is not only a company that sells hardware. It is also known for education. Cisco created the Cisco Networking Academy. This program trains students and professionals in networking skills. I see it as an investment in the future. People who complete Cisco training can earn certifications. These certifications, like CCNA (Cisco Certified Network Associate), show that someone has strong skills in networking. I believe this helps people find good jobs in technology.

Cisco’s influence is global. It has offices and customers around the world. Large corporations, small businesses, governments, and schools all use Cisco technology. I think this makes Cisco part of almost every sector. Without Cisco, many systems we use every day might not run as smoothly.

I also notice that Cisco is adapting to new trends. It invests in artificial intelligence, automation, and Internet of Things (IoT). IoT means connecting everyday objects, like cameras, sensors, or machines, to the internet. Cisco’s role is to make sure these connections are secure and efficient. I see this as the future of networking.

In summary, Cisco is a company that makes the internet work. It builds routers, switches, and security tools. It connects networks, protects data, and supports cloud services. It also trains people to build their careers in networking. I think of Cisco as a global leader in communication technology. For me, learning about Cisco is learning about the foundation of the digital world.

 

 

 

 

 

 

 

 

 

 

 

John’s Online Violin Studio – Cybersecurity Policy Documents

1. Governance & Purpose

This cybersecurity policy establishes rules and procedures to protect the confidentiality, integrity, and availability of data within John’s Online Violin Studio. The policy applies to all staff, students, contractors, and third-party partners using studio resources.

·         Objective: Ensure safe online teaching, performance, and business operations.

·         Scope: Covers studio websites, Thinkific courses, HeyGen/Unreal content, student information, financial records, and communications.

 

2. Acceptable Use Policy

·         Studio systems must be used for educational, performance, or administrative purposes only.

·         Do not install unauthorized software or plugins on studio devices.

·         Prohibit sharing of licensed music files, software, or personal student data without consent.

·         Students and staff must use secure logins when accessing studio platforms.

 

3. Access Control Policy

·         Authentication: Strong passwords (minimum 12 characters, mix of symbols/numbers/case).

·         Multi-Factor Authentication (MFA): Required for admin accounts on Thinkific, HeyGen, Unreal Engine projects, and cloud storage.

·         Least Privilege Principle: Students get access only to course materials; staff only to necessary admin tools.

·         Account Lifecycle: Remove inactive student and contractor accounts within 30 days.

 

4. Data Protection & Privacy

·         Collect only necessary student information (name, email, course enrollment, payment).

·         Store student data in encrypted databases or secured cloud services.

·         Prohibit recording or sharing student lessons without consent.

·         Comply with GDPR/CCPA where applicable for international students.

 

5. Network & Device Security

·         Secure Wi-Fi networks with WPA3 encryption.

·         Studio devices (computers, tablets, smartphones) must have updated firewalls and antivirus.

·         External USB devices must be scanned before connecting.

·         Use VPN when teaching or uploading material on public networks.

 

6. Risk Management & Incident Response

·         Conduct quarterly risk assessments (e.g., phishing attempts, password reuse).

·         Incident Response Steps:

o    Identify the incident (suspicious login, data breach).

o    Contain the threat (disable account, disconnect device).

o    Investigate with logs and forensic tools.

o    Notify affected users within 72 hours if data breach occurs.

o    Review and strengthen policies post-incident.

 

7. Training & Awareness

·         Annual cybersecurity awareness training for teaching staff.

·         Monthly reminders on safe password practices and phishing detection.

·         Encourage students to use secure platforms and avoid oversharing personal data.

 

8. Backup & Recovery

·         Daily automatic backup of course files, financial records, and website content.

·         Store backups in two locations: cloud + offline external drive.

·         Test recovery procedures quarterly.

 

9. Third-Party Vendor Security

·         Ensure Thinkific, HeyGen, Unreal Engine, and payment processors comply with international cybersecurity standards (ISO 27001, PCI DSS).

·         Review third-party data-sharing agreements annually.

 

10. Policy Review & Updates

·         Review policy annually or after major incidents.

·         Maintain version control and archive old versions.

·         Ensure all staff and contractors sign acknowledgment forms.

 

Deliverables for You (John):

1. A Master Cybersecurity Policy Document (above structure).
2. Separate Quick Reference Sheets for:

·         Teachers (best practices for device and data use).

·         Students (safe online learning guidelines).

·         Contractors (data access and confidentiality rules).

 

 

 

 

 

 

 

 

 

 

 

John’s Online Violin Studio

Personal Code of Ethical Conduct in Cybersecurity

1. Respect for Privacy

·         I will protect the privacy of all students, staff, and partners.

·         I will never share student recordings, personal data, or financial information without explicit consent.

·         I will use encrypted and secure systems to safeguard private communications.

 

2. Integrity and Honesty

·         I will present myself truthfully in all online activities.

·         I will not engage in plagiarism, piracy, or the unauthorized distribution of music, course materials, or digital content.

·         I will ensure that all my lessons, performances, and teaching resources are authentic and ethically sourced.

 

3. Responsibility in Technology Use

·         I will use cybersecurity tools responsibly to protect my studio and students.

·         I will avoid harmful actions such as hacking, spreading malware, or bypassing licensed software protections.

·         I will make decisions that prioritize the safety and well-being of my online music community.

 

4. Fairness and Equality

·         I will treat all students, staff, and collaborators with fairness and respect, regardless of background, culture, or ability.

·         I will ensure equal access to my online learning platforms, removing barriers where possible.

·         I will never misuse technology to give unfair advantage or disadvantage to anyone.

 

5. Protection of Intellectual Property

·         I will respect copyright laws in music, software, and digital media.

·         I will use licensed software for course delivery, recording, and performance.

·         I will credit composers, creators, and collaborators where acknowledgment is due.

 

6. Commitment to Safety

·         I will maintain strong cybersecurity practices: strong passwords, MFA, secure backups, and regular updates.

·         I will protect my online platforms from phishing, scams, and cyberattacks that could harm my students or their data.

·         I will respond quickly and ethically to any incident, prioritizing transparency and resolution.

 

7. Community and Professionalism

·         I will foster a safe, supportive, and inclusive online environment for learning and performance.

·         I will act with professionalism in communication, respecting cultural and personal boundaries.

·         I will use my role as a teacher, performer, and composer to inspire trust and confidence.

 

8. Continuous Improvement

·         I will stay informed about new cybersecurity threats and best practices.

·         I will integrate ethical digital citizenship lessons into my teaching, so students also learn safe online habits.

·         I will review and update this ethical code annually to keep it relevant and effective.

 

Closing Commitment (John’s Pledge):
As the founder of John’s Online Violin Studio, I pledge to uphold this personal code of ethical conduct. By protecting my students, respecting the digital rights of others, and practicing integrity in all online interactions, I will ensure that music education and performance remain safe, trustworthy, and inspiring in the digital world.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

John’s Online Violin Studio

IT Security Management Framework – Security Controls Evaluation

1. Governance and Compliance

Objective: Ensure studio operations meet ethical, legal, and professional standards.

·         Policies in Place: Cybersecurity Policy, Personal Ethical Code, Data Privacy Rules.

·         Controls:

o    Annual review of governance documents.

o    Compliance with GDPR/CCPA for international students.

o    Contracts with vendors (Thinkific, HeyGen, Unreal Engine, payment processors) checked for ISO 27001 / PCI DSS compliance.
Evaluation: Strong governance structure; requires regular audits to ensure vendors maintain compliance.

 

2. Access Control & Authentication

Objective: Protect systems, courses, and content from unauthorized use.

·         Controls:

o    Password policy (12+ characters, complexity required).

o    MFA on all admin accounts.

o    Role-based access (students, instructors, contractors).

o    Automatic account removal after inactivity (30 days).
Evaluation: Controls are appropriate but should include regular penetration testing to verify MFA effectiveness.

 

3. Data Security and Privacy

Objective: Secure personal, financial, and performance data.

·         Controls:

o    Data encryption (AES-256 for cloud storage).

o    Secure backups (cloud + offline external drives).

o    Consent forms for recordings and student data.

o    Limited data collection (minimum required for lessons/payments).
Evaluation: Effective; needs continuous monitoring for new privacy regulations in international teaching markets.

 

4. Network & Infrastructure Security

Objective: Ensure secure online delivery of lessons and content.

·         Controls:

o    WPA3-secured Wi-Fi for studio networks.

o    VPN use on public Wi-Fi.

o    Firewalls and antivirus on all devices.

• Restricted USB access with mandatory scanning.
  Evaluation: Appropriate; consider intrusion detection/prevention (IDS/IPS) for higher assurance.

 

5. Endpoint and Device Management

Objective: Protect laptops, tablets, phones used for teaching and performances.

·         Controls:

o    Automatic OS and software updates.

o    Device encryption enabled.

o    Remote wipe capability for lost devices.

o    Application whitelisting for studio-owned systems.
Evaluation: Adequate; a Mobile Device Management (MDM) solution could strengthen centralized control.

 

6. Incident Response and Digital Forensics

Objective: Detect, contain, and resolve security incidents quickly.

·         Controls:

o    Defined Incident Response Plan (Identify → Contain → Eradicate → Recover → Review).

o    Log collection for forensic analysis.

o    72-hour notification policy for breaches.

o    Post-incident review with lessons learned.
Evaluation: Solid framework; studio should run annual incident response drills.

 

7. Risk Management

Objective: Balance security measures with operational needs.

·         Controls:

o    Quarterly risk assessments.

o    Threat intelligence sources monitored (CISA alerts, vendor advisories).

o    Risk matrix scoring likelihood × impact.

o    Controls chosen based on risk outcomes (e.g., MFA for high likelihood credential attacks).
Evaluation: Works well; consider using lightweight GRC tools to document risks and mitigation.

 

8. Awareness & Training

Objective: Build a security-first culture among staff and students.

·         Controls:

o    Annual cybersecurity training for staff.

o    Monthly awareness reminders on phishing and password hygiene.

o    Student guides on safe online practices.
Evaluation: Good coverage; can be expanded with gamified training modules.

 

9. Evaluation & Continuous Improvement

Objective: Keep security posture adaptive and effective.

·         Controls:

o    Annual external audit of IT security.

o    Quarterly internal reviews of access, logs, and backups.

o    Policy updates after major incidents or platform changes.
Evaluation: Continuous improvement loop established; should include metrics (KPIs) like mean time to detect/respond, % of users with MFA, backup success rate.

 

Summary Evaluation:
Your online violin studio has a well-structured security control framework with strong governance, access management, and privacy practices. The main opportunities for improvement are:

1.        Introduce intrusion detection/prevention for networks.

2.        Centralize endpoint management (MDM).

3.        Perform regular penetration tests and response drills.

4.        Track KPIs for continuous improvement.