Learn: CompTIA Tech+ Lesson's 8-14 | Quizlet

Identify the problem.

Find out what the user's complaint is, making sure that you understand the background of the situation. When did the problem start? What accounts, hardware, and software are affected? Did anything change recently?

Conduct research.

This step can involve talking to people with knowledge of the problem, but it's mainly about reading reference guides online. For example, when facing the prospect of replacing a part on a laptop, a service manual for its make/model can be invaluable. Your company (or the company who made the device or software) may also have a knowledge base you can search.

Establish a theory.

That means coming up with an educated guess about the root cause. You don't have to be 100% certain at this point.

Test the theory.

Do what's needed to see if you were right in step 3. For example, if you suspect that a startup problem is happening because of a recent OS update, your plan might include a list of things that can correct such a problem, like rolling back an update or using Recovery Mode to set things right.

Establish a plan of action.

Decide what fixes you will try, and in what order. In general, start with the simplest and easiest things, because there's less time investment in doing them.

Implement or escalate.

Try out your ideas for fixing the problem to see what works. If you run out of ideas without resolving the problem, escalate the problem to someone with more knowledge or authority than you have, such as a supervisor or a senior technician.

Verify functionality.

After you correct the problem, go the extra mile to ensure that it is truly fixed. Ask the user to test it to confirm if possible. Then implement any preventive measures to minimize the likelihood of the problem reoccurring in the future.

Document your work.

As the old saying goes, the job isn't finished until the paperwork is done. Document the problem, the fix that worked, and any lessons learned from it. These notes will be helpful to other technicians who may encounter the same problem, either with this computer or similar ones.

No power to a device (Common Causes)

Device is unplugged, Battery is not charged, Power strip switch is off, Device has a physical problem.

No power to a device (Possible Solutions)

Ensure the device is receiving power, Charge the device's battery, Check device for physical damage, Investigate warranty repair options, Search online for troubleshooting tips specific to this issue for this device.

Device shuts down after a few minutes of use (Common Causes)

Device is overheating (A defective cooling fan, A detached heat sink, The device operating in a very warm environment).

Device shuts down after a few minutes of use (Possible Solutions)

Allow device to cool. Check cooling fans or heat sinks and clean dirty fans. Replace if needed.

Physical damage (Common Causes)

Device has been dropped or damaged.

Physical damage (Possible Solutions)

Order the part, and then refer to the service manual for the device for replacement instructions.

Device doesn't show up in the OS (Common Causes)

OS is not able to detect the device, or OS does not have a usable driver for the device.

Device doesn't show up in the OS (Possible Solutions)

Confirm that the device is properly installed or connected, and install a driver for the device.

Checking Windows System Files

Open an Administrator level command prompt, type sfc /scannow and press ENTER, wait for the utility to do its work (it will take several minutes), and read the report that appears letting you know whether problems were found and fixed.

macOS Recovery mode: Apple Silicon hardware

Turn on the Mac and hold down the power button for about 10 seconds and then release it. Then click Options.

macOS Recovery mode: Apple Intel hardware

Turn on the Mac and hold down the Command and R keys until you see Recovery Mode.

Utilities available in macOS Recovery Mode

Restore from Time Machine, Reinstall macOS (great for correcting system problems), Safari, and Disk Utility.

Hierarchical

A very rigid database structure that the Windows Registry uses

Non-relational

Database type used when managing diverse information that won't fit into a tabular structure

Object oriented

A database type enabling you to assign properties, relationships, and actions to database records

Relational

Database type used when there are multiple connected tables

Flat file

Database type consisting of a single table

Key Characteristics of a Database

Multiple concurrent users, scalability, speed in finding and retrieving data, and a variety of data elements.

Zero-Day Exploit

Immediately patching an OS as soon as the update is available can help prevent this type of attack.

Firewall

It can be either a hardware device or a software utility, and it thwarts some hacking attempts.

Inventory Management

This process lets you know what you have.

Difficult to Guess

If a password is strong, it has this quality.

Least Privilege

This principle states that excess privileges create unnecessary risk.

Security

client-side scripts, pop-ups, Flash media, certificate authority

Privacy

autofill form data, cookies, cached images and files, browser extensions

Confidentiality

Social engineering, Eavesdropping, Dumpster diving, Snooping, Wiretapping

Impersonation

Replay attack, Integrity, Unauthorized information alteration, Man-in-the-middle

Availability

Power outage, Destruction of equipment, Service outage, Hardware failure, Denial of service

Mandatory Access Control (MAC)

Access is determined by system-wide security policies. The system assigns security labels to resources and users and makes access decisions based on those labels. This model is best suited for highly secure networks such as those in government or military organizations.

Discretionary Access Control (DAC)

This model enables resource owners to determine who can access their resources and at what level. Access control lists (ACLs) or file permissions are typically used to make these assignments. This model is commonly used in everyday computing environments; it can be less restrictive and more flexible than MAC.

Role-Based Access Control (RBAC)

In this model, access to resources is based on roles and permissions. Users or entities are assigned specific roles, and each role is associated with a set of permissions. For example, the job of accounting clerk might come with access to accounting-related databases. This model is best suited for large organizations with complex access requirements, and where multiple people have the same job roles, requiring the same permissions.

Password generation

A password manager can generate random combinations of characters as passwords, eliminating vulnerabilities based on human factors such as ease of remembering and typing.

Password storage

A password manager can securely store all of a user's passwords in an encrypted database. The user needs only to remember one master password. The vault is encrypted, so if someone gains access to the vault file, they cannot read it without the master password.

Auto-fill and auto-login

When the user visits a website or app for which there is a stored password, the password manager can automatically fill in the credentials, saving users from typing them manually. This is not only convenient, but it also thwarts a keylogger, a type of malware that spies on users' keystrokes.

Cross-platform compatibility

Many password managers are available in versions for different operating systems, enabling users to access their passwords across all their devices and platforms.

Password auditing

A password manager can analyze the strength and security of existing passwords, as well as check for reuse and duplication.

Attribute-Based Access Control (ABAC)

This dynamic model evaluates a wide range of attributes (such as user, resource, and environmental) to make access control decisions. This model works well for complex access control scenarios such as in cloud computing and IoT environments.

Rule-Based Access Control (RBAC)

This model uses rules to determine access. The rules can be based on a combination of factors, such as user identity, time of day, and location. It is suitable for scenarios where fine-grained control is required.

Content-Based Access Control (CBAC)

This model focuses on controlling access to specific content within resources. Rather than focusing on the characteristics of who is requesting the access, it looks at the characteristics of the resource to be accessed.

Federated Access Control

This model, also called Federated Identity and Access Management (Federated IAM), is used in situations where multiple organizations or domains need to collaborate. It enables users from one organization to securely access resources in another organization without needing to authenticate separately.

Workstation log files

Collecting and examining the log files generated by individual instances of operating systems on specific devices that may be at risk.

Antimalware scanning

Monitoring the status and effectiveness of antivirus and antimalware software on individual devices.

Firewall activity monitoring

Monitoring the firewall on individual devices.

User account monitoring

Monitoring user account activities such as login attempts, password changes, and privilege modifications.

Endpoint detection and response

Monitoring endpoint devices (user hardware linked to the network) for unusual behavior or signs of compromise.

Email security monitoring

Scanning email communications for phishing attempts, malware attachments, and suspicious links.

Web security and filtering

Monitoring web traffic on individual devices.

Behavioral analysis

Using behavioral analysis tools to identify abnormal behavior patterns on individual devices.

Mobile device management

Monitoring the security of mobile devices such as smartphones and tablets.

Data loss prevention

Scanning for and blocking the unauthorized transmission of sensitive data from individual devices.

Something you know

A password or PIN

Something you are

A biometric factor

Non-repudiation

Digital signatures and timestamping are tools for this

Software token

A code sent to your smartphone to verify your identity

SSO

A centralized authentication mechanism that cuts down on sign-ins required

Something you have

A hardware token

Network traffic logs

These logs document network activities, including firewall logs, intrusion detection/prevention system logs, and network flow data. These logs can reveal suspicious or malicious network activity.

Web server logs

These logs record information about website access, including IP addresses, URLs, user agents, and HTTP status codes. They are essential for detecting web-based attacks such as SQL injection and cross-site scripting.

Authentication and authorization records

These records include login history, access control lists, and role assignments. They help in detecting unauthorized access and monitoring user activities.

Access and privilege change logs

These logs keep records of user access and privilege changes, including when users are added or removed from groups, role changes, and permissions granted or revoked.

Patch and update records

Records of software patching and system updates help ensure that systems are up to date with patches that can protect against known vulnerabilities.

User sign-in

The user signs into the identity provider (IdP), giving their credentials. The IdP is the system that manages the SSO process.

Issuing a token

The IdP issues an authentication token, also called a security token or SSO token. This token serves as proof of the user's authenticated session.

Storing the token

The token is stored on the user's device as a session token or a cookie.

Using the token for authentication

When the user attempts to access service providers that use the same SSO system, the token is presented, signing the user in automatically and invisibly.

Authorizing the user for the requested resources

The service provider trusts the IdP and validates the SSO token, after checking to ensure that the token is valid and not expired. The user is then granted access to the requested resource.

Bad habits

Frequent password changes can frustrate users and may lead them to choose weak passwords, to use predictable patterns for each change, or to store passwords in unsecure places, such as on paper at their desk or in unencrypted files. This can have the overall effect of weakening security, rather than strengthening it.

Memory burden

Users may have difficulty remembering multiple complex passwords, especially if they must change them frequently.

Reduced focus on more important measures

Overemphasis on password expiration can lead to neglect of other security measures that are more effective, such as multi-factor authentication.

Backup and recovery logs

These logs report the dates/times of backup and recovery activities, and can be helpful when a disaster occurs that requires performing a recovery operation.

User activity monitoring (UAM)

UAM solutions capture and log user activities such as file access, email communications, and app usage. These logs can be valuable for detecting insider threats.

Enhanced security

Even if a password is stolen or leaked, it becomes outdated soon, which limits the attacker's window of opportunity.

Reducing insider threats

When employees share their passwords with other employees, there's a risk of misuse. Requiring password change reduces that window of opportunity as well.

Compliance

Some regulatory standards and compliance frameworks require regular password changes, including PCI DSS (for credit card processing) and HIPAA (for medical records).

Enrollment

The individual's biometric data is captured and stored in a secure database.

Sampling

The individual requesting authentication provides a biometric sample.

Matching

The sample is compared to the stored reference data from the database.

Request

Someone claims a certain identity by offering credentials, such as username/password, a smart card, biometric data, or a security token.

Verification

The system checks the provided credentials against a database or an authentication service to confirm a match.

Access

The system grants access to the requested resources or services based on predefined permissions or policies.

Google Chrome

Click Customize and control Google Chrome (the three vertical dots to the right of the address bar), then Google Password Manager.

Microsoft Edge

Click Settings and more, Profiles, Passwords.

Apple Safari

Click Safari, Settings, and then click the Passwords icon.

VIRTUAL PRIVATE NETWORK

Used to connect remotely to your workplace network

SYMMETRIC-KEY ENCRYPTION

Cryptography with a single key

ENCRYPTING FILE SYSTEM

NTFS encryption feature

TRANSPORT LAYER SECURITY

Turns HTTP into HTTPS

CIPHER TEXT

Encrypted data

Symmetric-key cryptography process

1. Shared key generated. 2. Sender encrypts with shared key. 3. Encrypted message transmitted. 4. Receiver decrypts with same shared key. 5. Receiver reads content.

Asymmetric-key cryptography process

1. Sender gets receiver's public key. 2. Sender encrypts with public key. 3. Encrypted message sent. 4. Receiver decrypts with private key. 5. Receiver reads content.

BIA (Business Impact Analysis)

An assessment of the potential impact of identified risks on critical business functions.

Data backups

Copies of data files to be used for recovery in case of data loss.