| Technique | Description |
|---|---|
| Active Listening | Allow customer to complete explanations without interruption; take notes; repeat back key points for confirmation |
| Use Proper Language | Avoid jargon, acronyms, and slang; use terms customer can understand; speak clearly and professionally |
| Maintain Positive Attitude | Project confidence and competence; remain calm and patient; avoid arguing with customers |
| Set and Meet Expectations | Provide realistic timelines; communicate status updates; offer alternatives when unable to meet requests |
| Clarify Customer Statements | Ask open-ended questions; restate issues to confirm understanding; avoid assumptions |
| Step | Actions |
|---|---|
| 1. Identify the Problem | Gather information from user; identify symptoms; inquire about recent changes; determine if anything has changed; duplicate the problem if possible; approach multiple problems individually |
| 2. Establish a Theory | Question the obvious; consider multiple approaches; start with simple explanations; research knowledge bases |
| 3. Test the Theory | Confirm the theory; if theory is not confirmed, establish new theory or escalate |
| 4. Establish Plan of Action | Identify required resources; obtain approval if needed; create implementation plan; consider corporate policies |
| 5. Verify Full Functionality | Verify system operation; implement preventive measures; confirm with customer that issue is resolved |
| 6. Document Findings | Record problem description; document solution; update knowledge base; note lessons learned |
| Hazard | Safety Measures |
|---|---|
| Electrical Shock | Disconnect power before servicing; use ESD strap properly grounded; avoid working on live circuits; keep liquids away from equipment |
| Power Surges | Use surge protectors; install UPS for critical systems; verify proper grounding |
| Trip Hazards | Use cable management; secure cables with ties or raceways; mark cable pathways |
| Control | Purpose and Guidelines |
|---|---|
| MSDS/SDS | Material Safety Data Sheet/Safety Data Sheet provides handling, storage, and emergency procedures for chemicals; must be accessible for all hazardous materials |
| Temperature Control | Maintain 68-77°F (20-25°C) for equipment rooms; ensure adequate ventilation; monitor humidity levels 45-55% |
| Ventilation | Ensure proper airflow around equipment; maintain clear air intake and exhaust paths; use adequate HVAC systems |
| Item | Disposal Method |
|---|---|
| Batteries | Never dispose in regular trash; recycle at designated collection sites; lithium and alkaline batteries require special handling |
| Toner Cartridges | Return to manufacturer or use recycling programs; do not incinerate; avoid exposing to heat |
| CRT Monitors | Contains lead and other toxic materials; requires certified e-waste recycling facility; never landfill |
| Cell Phones/Tablets | Erase all data before disposal; use manufacturer take-back programs or certified e-waste recyclers |
| Hard Drives | Shred, degauss, or physically destroy before disposal; use certified e-waste facility for final disposal |
| Chemical Solvents | Follow MSDS disposal instructions; use hazardous waste collection services; never pour down drains |
| Principle | Implementation |
|---|---|
| User Privacy | Do not browse user files without permission; close private windows/applications when accessing system; respect confidentiality |
| Data Handling | Follow company policies for sensitive data; use encryption when required; secure data during repairs |
| Personal Information | Protect PII (Personally Identifiable Information); follow privacy regulations; obtain consent before accessing personal data |
| Policy Type | Key Elements |
|---|---|
| Acceptable Use Policy (AUP) | Defines appropriate use of company IT resources; specifies prohibited activities; outlines consequences for violations |
| Password Policy | Minimum length requirements; complexity requirements; expiration periods; prohibition of password sharing |
| Data Classification | Public, Internal, Confidential, Restricted categories; handling requirements for each level |
| BYOD Policy | Requirements for personal devices accessing corporate resources; security controls; data separation |
| Incident | Response Actions |
|---|---|
| Security Breach | Isolate affected systems; report to security team immediately; preserve evidence; do not power off systems; document all actions |
| Malware Infection | Disconnect from network; identify infected systems; quarantine affected devices; run antimalware scans; report to security team |
| Unauthorized Access | Lock account immediately; change credentials; review access logs; report to management and security team |
| Data Loss/Leak | Contain the leak; notify data protection officer; document scope; follow breach notification procedures |
| Step | Description |
|---|---|
| Request Form | Document proposed change, justification, impact assessment, and required resources |
| Approval Process | Submit to Change Advisory Board (CAB) or management; obtain sign-off before proceeding |
| Purpose of Change | Clearly define objectives and expected outcomes; align with business needs |
| Scope Definition | Identify affected systems, users, and services; determine boundaries of change |
| Risk Analysis | Assess potential impacts; identify mitigation strategies; plan rollback procedures |
| Implementation Plan | Schedule change window; coordinate with stakeholders; prepare step-by-step procedures |
| End-User Acceptance | Obtain user confirmation that change meets requirements; validate functionality |
| Type | Description |
|---|---|
| Full Backup | Complete copy of all selected data; archive bit cleared; longest backup time; fastest restore |
| Incremental Backup | Backs up only data changed since last backup (full or incremental); archive bit cleared; fastest backup; slower restore (requires full + all incrementals) |
| Differential Backup | Backs up data changed since last full backup; archive bit not cleared; moderate backup time; faster restore than incremental (requires full + last differential) |
| Concept | Definition |
|---|---|
| RTO (Recovery Time Objective) | Maximum acceptable time to restore service after disruption |
| RPO (Recovery Point Objective) | Maximum acceptable data loss measured in time; determines backup frequency |
| Cold Site | Backup facility with power and cooling but no equipment; longest recovery time; lowest cost |
| Warm Site | Backup facility with some equipment and connectivity; moderate recovery time and cost |
| Hot Site | Fully equipped backup facility ready for immediate failover; fastest recovery; highest cost |
| Regulation | Scope and Requirements |
|---|---|
| PCI DSS | Payment Card Industry Data Security Standard; protects credit card data; requires encryption, access controls, and regular security testing |
| GDPR | General Data Protection Regulation; EU regulation for personal data; requires consent, data minimization, right to deletion, breach notification |
| HIPAA | Health Insurance Portability and Accountability Act; protects healthcare information; requires encryption, access controls, audit logs, and training |
| Tool Type | Use Cases |
|---|---|
| RDP (Remote Desktop Protocol) | Windows remote access; port 3389; full desktop control; requires authentication |
| VNC (Virtual Network Computing) | Cross-platform remote desktop; port 5900; screen sharing and control |
| SSH (Secure Shell) | Secure command-line access; port 22; encrypted terminal sessions for Linux/Unix systems |
| Screen Sharing Software | Web-based or application-based remote control; often requires user permission to initiate |
| Element | Purpose |
|---|---|
| User Information | Name, contact details, department, location of person reporting issue |
| Device Information | Asset tag, model, serial number, hostname of affected equipment |
| Description | Detailed problem statement, symptoms, error messages, when issue started |
| Categories | Hardware, software, network, security classification for routing and reporting |
| Severity/Priority | Impact level and urgency; determines response time requirements |
| Status | Open, In Progress, Pending, Resolved, Closed tracking |
| Assignment | Technician or team responsible for resolution |
| Element | Details Recorded |
|---|---|
| Asset Tags | Unique identifier affixed to equipment; barcode or RFID for scanning |
| Inventory Lists | Database of all IT assets including hardware, software licenses, peripherals |
| Asset Information | Manufacturer, model, serial number, purchase date, warranty expiration, assigned user, location |
| Lifecycle Tracking | Procurement, deployment, maintenance, retirement stages |
| Control Type | Implementation |
|---|---|
| Badge Systems | ID cards with magnetic stripe or RFID for entry; track who enters and exits; revoke access immediately upon termination |
| Biometric Locks | Fingerprint, retina, or facial recognition; unique authentication; prevent credential sharing |
| Security Guards | Monitor entry points; verify identification; challenge unknown individuals |
| Mantraps | Double-door entry requiring first door to close before second opens; prevents tailgating |
| Door Locks | Key locks, cipher locks, or electronic locks on server rooms and restricted areas |
| Policy Element | Requirements |
|---|---|
| Enrollment | Register device with MDM system; install management profile; accept policy terms |
| Security Settings | Enforce password/PIN; require encryption; enable remote wipe capability |
| App Management | Approve allowed applications; block unauthorized apps; push corporate app updates |
| Container/Partition | Separate corporate and personal data; enforce policies only on corporate partition |
| Lost/Stolen Response | Report immediately; remote lock; remote wipe if necessary; deactivate corporate access |