- Security+ SY0-601 Certification
- Security+ SY0-601: Passing the Security+ Exam
- Security+ SY0-601: Definitions and Catchwords
- Security+ SY0-601: 1.0 Threats, Attacks, and Vulnerabilities
- Security+ SY0-601: 1.1 Social Engineering Techniques
- Security+ SY0-601: 1.2 Indicators of Attack
- Security+ SY0-601: 1.3 Application Attacks
- Security+ SY0-601: 1.4: Network Attack Indicators
- Security+ SY0-601: 1.5: Threat Actors, Vectors, and Intelligence Sources
- Security+ SY0-601: 1.6: Vulnerabilities
- Security+ SY0-601: 1.7: Security Assessment
- Security+ SY0-601: 1.8: Penetration Testing
- Security+ SY0-601: 2.0 Architecture and Design
- Security+ SY0-601: 2.1 Enterprise Security Architecture
- Security+ SY0-601: 2.2: Virtualization and Cloud Security
- Security+ SY0-601: 2.3: Secure Application Development, Deployment and Automation
- Security+ SY0-601: 2.4: Authentication and Authorization
- Security+ SY0-601: 2.5: Implementing Cybersecurity Resilience
- Security+ SY0-601: 2.6: Embedded and Specialized Systems
- Security+ SY0-601: 2.7: Physical Security Controls
- Security+ SY0-601: 2.8: Cryptography
- Security+ SY0-601: 3.0: Implementation
- Security+ SY0-601: 3.1 Secure Protocols
- Security+ SY0-601: 3.2: Host and Application Security
- Security+ SY0-601: 3.3: Secure Network Design
- Security+ SY0-601: 3.4: Wi-Fi Security
- Security+ SY0-601: 3.5: Secure Mobile Solutions
- Security+ SY0-601: 3.6: Cybersecurity Solutions in the Cloud
- Security+ SY0-601: 3.7: Identity and Account Management Controls
- Security+ SY0-601: 3.8: Implement Authentication and Authorization Solutions
- Security+ SY0-601: 3.9: Public Key Infrastructure
- Security+ SY0-601: 4.0: Operations and Incident Response
- Security+ SY0-601: 4.1: Tools to Assess Organizational Security
- Security+ SY0-601: 4.2: Policies, Processes, and Procedures for Incident Response
- Security+ SY0-601: 4.3: Appropriate Data Sources for Investigation
- Security+ SY0-601: 4.4: Mitigation Techniques
- Security+ SY0-601: 4.5: Digital Forensics
- Security+ SY0-601: 5.0: Governance, Risk, and Compliance
- Security+ SY0-601: 5.1: Types of Controls
- Security+ SY0-601: 5.2 Regulations, Standards, and Frameworks
- Security+ SY0-601: 5.3: Policies and Organizational Security
- Security+ SY0-601: 5.4: Risk Management Processes and Concepts
- Security+ SY0-601: 5.5: Privacy and Sensitive Data
- Security+: My Favorite Free Tools
- Security+ : Sample Questions
- Passing the CompTIA Exams
- Understanding CompTIA Objectives Using Bloom’s Taxonomy
A Note About “Inclusive Language”
In today’s highly politically-charged environment, the words “white“, “black” and “gray” (or “grey”) are no longer allowed. This means we can’t use terms like White Hat, Black Hat or Gray Hat. Instead we must use “Allowed“, “Not Allowed” or “Partially Allowed“. Military terms are off limits. No more DMZ.
Deprecated Terminology and Updated Terminology
| White Hat Hacker | Authorized Hacker |
| Black Hat Hacker | Unauthorized Hacker |
| Gray Hat Hacker | Partially Authorized Hacker |
| Whitelist | Allow list/Approved list |
| Blacklist | Block list/Deny list |
| White box | Known environment |
| Black box | Unknown environment |
| Grey box | Partially known environment |
| Mantrap | Access Control Vestibule |
| Demilitarized Zone (DMZ) | Screened subnet |
| Man-in-the-Middle/Man-in-the-Browser | On-path Attack |
Be A Ninja With The OSI/DoD Models
Ports, well-known and otherwise
NAT and Private Address Ranges (thanks JP)
Know the Basic Terminology
Asset – anything valuable, such as information, software or a car stereo
Threat – any event or object that might result in a loss, like theft or fire damage
Threat Agent – any person or thing that can carry out a threat, like a thief or a flood
Vulnerability – a weakness in security, like an unprotected server or a hole in a fence
Exploit – a way to actually take advantage of a weakness, for instance by attacking an unprotected server or going through that hole in the fence
Risk – the likelihood that that an exploit will actually be performed
Risk management is what it’s all about: how much risk can you tolerate, and how much will you spend to avoid it?
Information Security Provides
According to CompTIA:
-
- Confidentiality – Only authorized persons have access to the information.
- Integrity – Insurance that a message, software or other item hasn’t been changed in any way.
- Availability – Information is available to properly authorized users.
Other sources discuss:
-
-
- Privacy – Only authorized persons know that information exists. Security practices acknowledge the importance of Privacy, but security certifications walk glassy-eyed right past it.
- Non-repudiation -The impossibility of denying that information comes from a specific source.
- Authenticity – An affirmation that information is intact (has Integrity) and comes from the stated source (Non-repudiation). CompTIA does not use this term, but it’s common on other tests, e.g. the CEH.
-
While proper IAM (Identity and Access Management) provides these benefits:
-
-
- Authentication – Providing both a username (Identification) and a password or something similar (Authentication).
- Authorization – The permissions granted by the entity providing access, for instance share access permissions in Active Directory. People also call this Permissions, though usually that’s more correctly applied to individual settings rather than the collective environment of Authorization. See how smart you are now?
- Audit/Accounting – The ability to review accesses and actions of resources.
-
Basic Security Concepts
Layering -Providing multiple layers of protection: physical access control, a firewall, antivirus software, etc. The key concept is preventing one layer’s configuration from compromising other layers. If you leave workstations logged in overnight to distribute antivirus updates, you’ve weakened security with that compromise.
Limiting – Basically, limiting access, whether physical or logical.
Diversity – Using more than one type of a given security method; for instance, both a physical and a software firewall.
Obscurity – Limiting the information available to attackers. For example, your web server should not reveal that it’s Apache 1.2.
Simplicity – Put simply, don’t make your security layers hard to understand or configure.
Very Non-Basic Security Concepts
Trust Analysis
https://www.infosecisland.com/blogview/17011-Broken-Trust-Part-2-Applying-the-Approach-to-Dropbox.html
The Moebius Defense / Defense in Depth