Everyday Guidebooks
Cover of CompTIA Security+ for Beginners

Cybersecurity & IT

CompTIA Security+ for Beginners: Learn the Language of Security

A Plain-English Vocabulary Guide to Threats, Controls, Identity, Cryptography, and Incident Response

by Todd Michael

Available now

Searching for comptia security+ for beginners but finding that every explanation seems to introduce five more unfamiliar terms? Start here.

Before you tackle an exam-focused study plan, build a vocabulary you can actually use. This plain-English guide introduces the language of security controls, common threats, identity and access, cryptography, and incident response. Short workplace scenarios show how the pieces fit together: why a stolen password matters, what encryption can and cannot protect, and how a team responds when an incident unfolds.

Each chapter explains related terms in context, distinguishes easily confused concepts, and gives you opportunities to practice recognizing them. You will finish with a clearer mental map and a foundation for choosing your next study resources.

This is an independent, unofficial learning resource, not a comprehensive exam-preparation guide. CompTIA and Security+ are trademarks of CompTIA, Inc., which does not endorse or sponsor this book.

Contents
  1. 1. Learning to Speak Security
  2. 2. Assets, Exposure, and Risk
  3. 3. Security Controls and Defense in Depth
  4. 4. Threat Actors and Their Methods
  5. 5. Malware, Vulnerabilities, and Exploitation
  6. 6. Identity, Authentication, and Authorization
  7. 7. Managing Access Across the Organization
  8. Accounts, Permissions, and Roles
  9. Least Privilege: Enough, Not Everything
  10. Separation of Duties: Sharing Responsibility
  11. Provisioning Access
  12. A Joiner, a Mover, and a Leaver
  13. Access Reviews: Checking What Exists
  14. Shared and Privileged Accounts
  15. Access Is a Continuing Decision
  16. 8. Network Security Language
  17. 9. Protecting Systems and Data
  18. 10. Cryptography Without the Mystery
  19. 11. Certificates, Signatures, and Trust
  20. 12. Seeing and Investigating Security Events
  21. 13. Incident Response and Recovery
  22. 14. Connecting the Vocabulary
  23. Scenario: A Sign-In That Does Not Fit
  24. Scenario: The Shared Workstation
  25. Scenario: A Trustworthy-Looking Website
  26. Scenario: A Role Change and an Unexpected Download
  27. A Practical Vocabulary Review
  28. Moving Toward an Exam-Focused Study Plan
  29. Other Books by Todd Michael

Read a sample: 1. Learning to Speak Security

A small bakery opens early, but its owner cannot view the day’s custom orders. The shared computer is running, the internet connection appears to be working, and the order file is where it usually lives. When she opens it, however, the information is scrambled.

At first, the problem might sound like a computer problem. It is also a security question. The bakery depends on information being usable and correct. If the order file has been changed, damaged, or made unavailable, the business may struggle to serve its customers.

The owner does not yet know what happened. An employee might have accidentally overwritten the file. A software problem might have damaged it. Someone might have deliberately altered it. Each possibility calls for different questions, but all of them can be discussed with the same basic vocabulary.

That vocabulary is the starting point of this book. Security language gives you a way to describe what matters, what could go wrong, and what might reduce the harm. You do not need a technical background to begin using it. You need a few clear distinctions and a willingness to ask what a term means in the situation in front of you.

An asset is something that has value to a person or organization and may need protection. An asset can be physical, digital, or less tangible.

For the bakery, assets include the ovens, the point-of-sale system, the website, and the computer used to manage orders. They also include the order information itself: customer names, contact details, pickup times, and special instructions. The bakery’s reputation and its ability to operate are valuable, too, even though they cannot be placed on a shelf or opened as a file.

Calling something an asset does not mean it is valuable in every possible way. A public menu is intended to be seen, so keeping its contents secret may not matter. The menu still needs to be accurate: an incorrect price or allergen description could cause problems. A customer’s contact information, on the other hand, may require both accuracy and restricted access.

This is an important habit: do not stop at naming an asset. Ask what about it needs protection? The answer might be secrecy, accuracy, access when needed, or a combination of these.

Assets also depend on one another. The order file may be stored on a computer, accessed through an account, and supported by an internet service. A problem affecting any of those supporting pieces could interfere with the bakery’s use of the information.

The next terms are often used as if they mean the same thing. They do not. Keeping them separate makes a security conversation much easier to follow.

A threat is a potential cause of harm. It could be a person who wants to steal customer information, an employee who makes a mistake, a fire, or a software failure. Some threats involve deliberate action; others do not.

A vulnerability is a weakness that could be used or taken advantage of by a threat, or that could otherwise contribute to harm. An outdated application with an uncorrected flaw may contain a vulnerability. So may a shared account whose password is known by people who no longer work at the bakery. A vulnerability is not the same as an actual break-in or mistake. It is a condition that can make an unwanted outcome possible or more likely.

Risk is the possibility of loss or harm when a threat affects something valuable, taking into account how likely the outcome is and how much impact it could have. Risk is not just a list of scary things that might happen. It connects a possible event to a consequence.

A control is a safeguard or measure intended to manage risk. Controls can reduce the chance of an unwanted event, help someone notice it, limit its effects, or support recovery afterward. A control does not have to be a piece of software. A process for reviewing access, a locked door, and a tested backup can all serve as controls.

Consider the bakery’s order file again:

- Asset: The order information and the system that makes it available. - Threat: An employee might accidentally delete or overwrite the file. - Vulnerability: Everyone edits the same file, and there is no usable previous copy. - Risk: The bakery could lose order details, delay pickups, and spend time reconstructing the schedule. - Control: The bakery could keep protected backup copies and periodically test whether it can restore them.

The control addresses an important part of the problem, but it has limits. A backup may help restore a damaged file; it does not necessarily prevent someone from changing the original. A backup that is incomplete, inaccessible, or never tested may also fail when needed. The bakery might combine backups with controls over who can edit orders and a process for checking changes.

Notice that the same asset can face several threats and have several vulnerabilities. Someone outside the bakery might try to steal the order file. An employee might accidentally alter it. A computer failure might make it unavailable. The appropriate response depends on which outcome the bakery is trying to prevent or manage.

It is also possible for a weakness to exist without being exploited. A poorly protected account is a concern even if there is no evidence anyone has misused it. Conversely, harm can occur without a malicious attacker. Security work includes…

More Cybersecurity & IT

Cover of The White Hat Bible, Volume 1The White Hat Bible, Volume 1Available nowCover of The White Hat Bible, Volume 2The White Hat Bible, Volume 2Available nowCover of The White Hat Bible, Volume 3The White Hat Bible, Volume 3Available nowCover of The White Hat Bible, Volume 4The White Hat Bible, Volume 4Available nowThe White Hat Bible, Volume 5Available nowCover of The White Hat Pocket GuideThe White Hat Pocket GuideAvailable now

About Todd Michael

Todd Michael is an American author and the founder of ToddMichael.tv. He writes practical, plain-English books on money, health, preparedness, technology, games, humor and more.

About the author Todd Michael · Todd Michael’s author site

Part of the ToddMichael.tv network.