IT FundamentalsA+

Privacy, Licensing, and Policy for CompTIA A+ 220-1102

Privacy laws, software licensing, and acceptable use policies govern IT operations. CompTIA A+ 220-1102 tests software licensing types, PII protection requirements, AUP enforcement, and incident reporting obligations. This guide covers every privacy and licensing concept in the A+ Core 2 objectives.

8
5 sections · 8 exam key points
1 practice questions

Software Licensing

Software licensing defines how software may be used. License types: Commercial/Retail: purchased for a fixed number of devices (per-seat or per-device). Must comply with the license agreement. OEM (Original Equipment Manufacturer): sold with hardware, tied to that device — cannot be transferred to another computer. Generally cheaper than retail but non-transferable. Volume licensing: enterprise contracts allowing installation on many devices (Microsoft Select, Open License, Enterprise Agreement). Open source: source code is publicly available. Sub-types: Free to use, modify, and distribute (GPL, MIT, Apache, BSD). GPL: derivative works must also be GPL (copyleft). MIT/BSD/Apache: permissive — derivative works can be proprietary. Freeware: free to use, no source code access, not open source (example: Adobe Reader older versions). Shareware: try before you buy — limited trial period or features. Subscription: paid recurring fee (Microsoft 365, Adobe Creative Cloud). License portability: Microsoft 365 allows installation on multiple devices under one subscription — check license terms. Software Asset Management (SAM): ensures all software is properly licensed — avoids audit penalties.

PII (Personally Identifiable Information)

PII: any information that can identify a specific individual. Examples: name, email, phone number, social security number, date of birth, address, IP address, biometric data, financial account numbers, medical records. PHI (Protected Health Information): PII related to health conditions — protected by HIPAA. PCI (Payment Card Industry): standards protecting credit card data. Why PII matters for A+ technicians: when providing support, technicians may encounter PII on user screens, in databases, or on files. Technicians must handle PII carefully: minimum access necessary, do not copy or share unnecessarily, do not leave PII visible on unattended screens, report accidental exposure. Data retention policies: organizations must retain some records for compliance (HIPAA: 6 years, financial: 7 years) and securely dispose of data no longer needed. Right to be forgotten (GDPR): individuals can request deletion of their personal data. Cloud data location: data sovereignty — some regulations require data to be stored in specific countries.

Regulations and Compliance

HIPAA (Health Insurance Portability and Accountability Act): U.S. regulation. Protects PHI. Requires access controls, audit logging, encryption, and breach notification. Penalties: $100–$50,000 per violation. GDPR (General Data Protection Regulation): EU regulation. Applies to any organization handling EU residents' data. Requires consent, data minimization, breach notification within 72 hours. CCPA (California Consumer Privacy Act): U.S. state law giving California residents rights over their personal data. PCI-DSS (Payment Card Industry Data Security Standard): not a government law — industry standard for organizations handling payment cards. Requires encryption, network segmentation, access controls, regular audits. FERPA (Family Educational Rights and Privacy Act): protects student educational records. SOX (Sarbanes-Oxley): financial reporting and record-keeping requirements for public companies. Incident reporting obligations: many regulations require breach notification — HIPAA within 60 days to HHS, GDPR within 72 hours to supervisory authority.

Acceptable Use Policy (AUP)

AUP: written policy that users must agree to before using organizational IT resources. Covers: permitted and prohibited use of company equipment, networks, email, and internet access. Examples of prohibited activities: accessing illegal content, installing unauthorized software, using company systems for personal business, bypassing security controls, sharing credentials. AUP enforcement: technical controls enforce much of the AUP (content filtering, application whitelisting, MDM). Policy violations: documented in HR records, may result in disciplinary action up to termination. Technical monitoring: many organizations monitor internet usage, email, and system activity. Users should have no expectation of privacy on company systems — the AUP typically states this explicitly. Mobile device AUP: covers both corporate-issued and BYOD devices. Personal use limitations for BYOD devices. New hire onboarding: AUP signed at hiring, reviewed periodically. Refresh training when policy changes.

Incident Reporting and Ethics

Mandatory reporting scenarios: Discovered child exploitation material: mandatory report to law enforcement (NCMEC CyberTipline in US) regardless of who it belongs to. Personal data breach: mandatory reporting to regulatory bodies (HIPAA: HHS, GDPR: supervisory authority) and affected individuals. Illegal activity on company systems: follow company policy — typically involves HR, legal, and management before involving law enforcement. Ethics in IT: do not use admin credentials to snoop in user accounts beyond what's necessary for the support task. Honest documentation: accurately document what was done and found — don't cover up mistakes. Protecting confidential information: client and employer information is confidential — NDAs and fiduciary duty apply. Code of ethics: CompTIA's IT Professional Code of Ethics emphasizes: honesty, integrity, objectivity, competence, confidentiality, and respecting laws. Social media and public statements: don't share client/employer confidential information on social media.

Key exam facts — A+

  • OEM license: tied to the device, cannot be transferred
  • GPL: copyleft — derivative works must also be GPL; MIT/Apache: permissive
  • PII: any information that identifies an individual — must be protected
  • HIPAA: protects PHI; GDPR: EU data protection; PCI-DSS: payment card security
  • AUP: users have no expectation of privacy on company systems
  • Child exploitation material: mandatory report to law enforcement
  • Data breach notification: HIPAA within 60 days to HHS; GDPR within 72 hours
  • Software SAM: ensures all software is properly licensed — prevents audit penalties

Common exam traps

Practice questions — Privacy & Licensing

These questions are representative of what you will see on A+ exams. The correct answer and explanation are shown immediately below each question.

Q1.

A.A. No problem — OEM licenses can be transferred freely
B.B. OEM licenses are tied to the original hardware and cannot be transferred to a new device
C.C. OEM licenses are the same as retail licenses
D.D. The license must be registered online before transfer

Explanation: OEM (Original Equipment Manufacturer) licenses are tied to the specific hardware they were sold with. Using an OEM license from one computer on a different computer violates the license agreement. A retail or volume license should be used for deployment to different hardware.

Frequently asked questions — Privacy & Licensing

What should an A+ technician do if they accidentally see PII on a user's screen while helping with an unrelated issue?

Acknowledge the sensitivity, do not take notes or photographs of the PII, do not share it with others, and continue with the support task while minimizing further exposure. If the PII relates to a possible data breach (e.g., the file was improperly placed in a public location), report the finding to your supervisor per the organization's data breach response policy.

Practice this topic

Test yourself on Privacy & Licensing

JT Exams routes you to questions in your exact weak areas — automatically, after every session.

No credit card · Cancel anytime

Related certification topics