Lesson Sixteen

Secure Communication Channels, Remote Access, and Third-Party Connectivity

SierraTec Secure CISSP Certification Preparation Course

Lesson Overview

Modern organizations rarely operate entirely within one trusted physical location.

Employees work remotely. Administrators manage systems from centralized consoles. Organizations exchange data with banks, suppliers, cloud providers, telecommunications carriers, managed service providers, and business partners. Voice and video meetings cross the Internet. Satellite and cellular connections support remote facilities. Vendors may require temporary privileged access to repair critical equipment.

Every one of these connections creates a potential trust boundary.

The security objective is not simply:

“Encrypt the connection.”

A secure communication channel must also consider:

• who is communicating;
• which device is being used;
• what resource may be accessed;
• whether the endpoint is trustworthy;
• which protocol protects the communication;
• whether access is appropriately limited;
• how the session is monitored;
• what happens if the connection is compromised;
• when the connection or authorization should terminate.

The current CISSP Examination Outline places these topics under Domain 4, Objective 4.3 — Implement secure communication channels according to design. The objective currently identifies four broad areas:

• voice, video, and collaboration technologies;
• remote access and network-administrative functions;
• data communications such as backhaul and satellite links;
• third-party connectivity, including telecommunications providers and hardware-support connections.

NIST's remote-access guidance emphasizes that remote users may include employees, contractors, partners, and vendors, and that both remote-access technologies and client devices should be protected according to their expected threats.

NIST Zero Trust guidance further emphasizes that network location alone should not create implicit trust. User and device authentication and authorization should occur before access to enterprise resources is established.

The central Lesson Sixteen question is:

How should remote users, administrators, collaboration systems, telecommunications links, partners, and vendors communicate with organizational resources without weakening confidentiality, identity, segmentation, least privilege, monitoring, or availability?

CISSP Exam Objective Alignment

Learning Objectives

After completing this lesson, you should be able to:

1. Define a secure communication channel.
2. Explain why encryption alone does not make a channel secure.
3. Identify major remote-access risks.
4. Explain remote-access gateways.
5. Explain client-based VPNs.
6. Explain site-to-site VPNs.
7. Explain IPsec VPNs.
8. Explain TLS-based remote access.
9. Distinguish full tunneling from split tunneling.
10. Explain the security tradeoffs of split tunneling.
11. Explain why MFA is important for remote access.
12. Explain device posture assessment.
13. Explain Zero Trust Network Access.
14. Distinguish VPN access from resource-specific Zero Trust access.
15. Explain SSH for administrative access.
16. Explain RDP security considerations.
17. Explain why directly exposing administrative services is dangerous.
18. Explain bastion hosts.
19. Explain jump servers.
20. Explain privileged-access workstations.
21. Explain administrative-network segmentation.
22. Explain session recording and privileged-session monitoring.
23. Explain temporary and just-in-time administrative access.
24. Explain voice-over-IP security.
25. Explain signaling versus media in VoIP.
26. Explain SIP conceptually.
27. Explain secure voice-media concepts.
28. Explain video-conferencing risks.
29. Explain collaboration-platform security.
30. Explain conference-room device risk.
31. Explain screen-sharing and recording controls.
32. Explain meeting authentication and authorization.
33. Explain data communications.
34. Explain private network circuits.
35. Explain backhaul networks.
36. Explain redundancy in communication paths.
37. Explain satellite-network security considerations.
38. Explain latency and availability implications of satellite links.
39. Explain third-party connectivity.
40. Explain telecommunications-provider risk.
41. Explain vendor remote-support risk.
42. Explain hardware-maintenance access.
43. Apply least privilege to third-party connectivity.
44. Explain third-party network segmentation.
45. Explain time-bounded access.
46. Explain connection monitoring.
47. Explain information-exchange agreements.
48. Explain third-party connection termination.
49. Explain how secure channels support confidentiality, integrity, authentication, and availability.
50. Solve CISSP-style secure-communications scenarios.

Part I — What Is a Secure Communication Channel?

1. Communication Creates Exposure

Information may travel across:

• the public Internet;
• wireless networks;
• telecommunications carriers;
• satellite networks;
• partner networks;
• third-party systems.

Each path may contain infrastructure not controlled by the organization.

2. Secure Channel Objectives

A secure communication channel may need to provide:

                 SECURE CHANNEL

                       │

       ┌───────────────┼───────────────┐

       ▼               ▼               ▼

CONFIDENTIALITY     INTEGRITY      AUTHENTICATION

       │               │               │

       └───────────────┼───────────────┘

                       ▼

                   AVAILABILITY

Depending on the use case, accountability and nonrepudiation may also matter.

3. Encryption Alone Is Not Enough

Suppose an encrypted tunnel connects:

Attacker → Enterprise

If the attacker obtained valid credentials, encryption protects the attacker's communication from interception.

Therefore:

Encryption protects a channel. It does not automatically determine whether the communicating party should be trusted.

4. Complete Secure-Channel Model

IDENTITY

   +

DEVICE

   +

AUTHORIZATION

   +

ENCRYPTION

   +

SEGMENTATION

   +

MONITORING

   +

SESSION LIFECYCLE

   =

SECURE COMMUNICATION

Part II — Remote Access

5. What Is Remote Access?

Remote access allows a user or system outside the normal enterprise environment to access organizational resources.

Remote users may include:

• employees;
• contractors;
• administrators;
• business partners;
• vendors.

NIST specifically recognizes these groups as common users of enterprise remote-access technologies.

6. Remote-Access Architecture

REMOTE USER

     │

     ▼

UNTRUSTED NETWORK

     │

     ▼

REMOTE-ACCESS GATEWAY

     │

     ▼

AUTHENTICATION

     │

     ▼

POLICY / POSTURE

     │

     ▼

AUTHORIZED RESOURCES

7. Remote Access Expands the Perimeter

Traditional thinking:

OFFICE = INSIDE

INTERNET = OUTSIDE

Modern reality:

USERS

DEVICES

APPLICATIONS

CLOUD SERVICES

PARTNERS

      │

      ▼

DISTRIBUTED ENVIRONMENT

This is one reason Zero Trust emphasizes identity and resource protection over simple network location.

Part III — Remote-Access Threats

8. Credential Theft

Remote-access credentials are valuable because they can potentially provide attackers with legitimate-looking access.

Mitigations include:

• MFA;
• phishing-resistant authentication where appropriate;
• anomaly detection;
• credential lifecycle management.

9. Compromised Endpoint

A valid employee can connect using:

an infected laptop.

Therefore remote-access security should consider:

• user identity;
• device identity;
• endpoint security posture.

10. Untrusted Networks

Remote users may connect through:

• hotels;
• airports;
• public Wi-Fi;
• home networks.

NIST notes that telework devices commonly operate on networks not controlled by the organization and should be secured accordingly.

11. Exposed Remote Services

Direct Internet exposure of remote-management services can create major risk.

CISA notes that attackers commonly exploit poorly secured remote desktop services, VPNs, compromised credentials, and remote-management software for initial access.

Part IV — VPN Fundamentals

12. Virtual Private Network

A VPN creates a protected logical communication channel across another network.

REMOTE CLIENT

     │

     ▼

=========================

  ENCRYPTED VPN TUNNEL

=========================

     │

     ▼

VPN GATEWAY

     │

     ▼

ENTERPRISE

13. VPN Security Services

A VPN can support:

• confidentiality;
• integrity;
• endpoint authentication.

But VPN security depends on:

• credentials;
• endpoint security;
• protocol configuration;
• authorization.

Part V — Remote-Access VPN

14. Client-to-Site VPN

A remote-access or client VPN connects an individual endpoint to an enterprise gateway.

LAPTOP

  │

  ▼

INTERNET

  │

  ▼

VPN GATEWAY

  │

  ▼

CORPORATE NETWORK

15. Security Considerations

Remote VPN access should consider:

• MFA;
• device posture;
• session timeout;
• authorization;
• logging;
• least privilege.

Part VI — Site-to-Site VPN

16. Site-to-Site Model

OFFICE A

   │

VPN GATEWAY

   │

================

 IPsec TUNNEL

================

   │

VPN GATEWAY

   │

OFFICE B

Users may not run VPN software individually because gateways protect traffic between sites.

17. Site-to-Site Use Cases

Examples:

• headquarters to branch office;
• enterprise to cloud environment;
• organization to trusted partner.

Part VII — IPsec

18. IPsec Review

IPsec protects network-layer communications.

It can support:

• confidentiality;
• integrity;
• authentication;
• anti-replay protection.

19. Tunnel Mode

For site-to-site VPN use, tunnel mode is common.

NEW IP HEADER

      │

   IPsec

      │

ORIGINAL IP PACKET

The original packet is encapsulated.

20. Transport Mode

Transport mode protects the payload of the original IP packet without creating the same full new outer tunnel structure.

Part VIII — TLS-Based Remote Access

21. TLS VPN / Secure Portal Concepts

Remote access can also use TLS-protected application sessions.

Possible implementations include:

• secure web portals;
• application gateways;
• browser-accessible systems.

22. Advantage

Application-focused remote access can sometimes avoid giving a user broad network-level connectivity.

Example:

USER

 │

 ▼

TLS ACCESS GATEWAY

 │

 ▼

AUTHORIZED HR APPLICATION



      X



ENTIRE INTERNAL NETWORK

Part IX — Full Tunneling

23. Full Tunnel

With full tunneling:

Most or all applicable client traffic is sent through the enterprise VPN.

REMOTE LAPTOP

      │

      ▼

 VPN TUNNEL

      │

      ▼

ENTERPRISE SECURITY

      │

      ├── Internal resources

      └── Internet access

24. Benefits

Full tunneling can improve:

• centralized monitoring;
• policy enforcement;
• web filtering.

25. Cost

It may increase:

• bandwidth consumption;
• latency;
• VPN-gateway load.

Part X — Split Tunneling

26. Split Tunnel

Split tunneling permits some traffic through the enterprise VPN while other traffic accesses external destinations directly.

REMOTE LAPTOP

     │

     ├──► VPN ──► CORPORATE APPS

     │

     └───────► INTERNET

27. Benefit

Split tunneling may reduce:

• VPN bandwidth;
• latency;
• enterprise gateway load.

28. Security Concern

The remote endpoint may simultaneously connect to:

• enterprise resources;
• untrusted networks.

This can reduce centralized security visibility and potentially create a bridging risk.

29. CISSP Principle

Do not answer:

Split tunneling is always wrong.

Ask:

• What is the risk?
• What endpoint controls exist?
• What monitoring is required?
• What business requirement exists?

Part XI — Remote-Access Authentication

30. MFA

Because remote access crosses an external trust boundary, strong authentication is especially important.

PASSWORD

   +

AUTHENTICATOR / TOKEN

   +

OPTIONAL DEVICE SIGNALS

      │

      ▼

REMOTE ACCESS DECISION

31. Identity Is Not Authorization

Authentication answers:

Who are you?

Authorization answers:

What may you access?

Remote access should not automatically provide:

the entire enterprise network.

Part XII — Endpoint Posture

32. Remote Device Condition

Before granting sensitive access, policy may consider:

• EDR running;
• supported OS;
• patches;
• disk encryption;
• device management;
• certificate status.

33. Identity + Device

AUTHORIZED USER

      +

MANAGED HEALTHY DEVICE

      +

APPROPRIATE CONTEXT

      │

      ▼

ACCESS

Part XIII — Zero Trust Network Access

34. ZTNA Concept

Zero Trust Network Access generally focuses on granting access to:

specific authorized resources

rather than extending broad network trust.

NIST emphasizes that Zero Trust removes implicit trust based solely on network location and authenticates/authorizes users and devices before sessions to resources are established.

35. Traditional VPN Model

USER

 │

 ▼

VPN GATEWAY

 │

 ▼

NETWORK ACCESS

 │

 ▼

MULTIPLE RESOURCES

36. Resource-Focused Model

USER + DEVICE

      │

      ▼

POLICY DECISION

      │

      ▼

APP A



APP B → NOT AUTHORIZED

DB C  → NOT EXPOSED

37. Important Distinction

VPN:

creates a protected network path.

Zero Trust:

is an access-control architecture and security philosophy.

They are not simply interchangeable terms.

Part XIV — Remote Administrative Access

38. Administrative Connections Are Higher Risk

Administrators can potentially:

• modify configurations;
• create users;
• disable security;
• access sensitive information.

Therefore remote administrative access should normally receive stronger protection than ordinary user access.

39. Administrative Access Model

ADMINISTRATOR

      │

      ▼

STRONG AUTHENTICATION

      │

      ▼

PRIVILEGED ACCESS GATEWAY

      │

      ▼

JUMP SERVER

      │

      ▼

AUTHORIZED TARGET

Part XV — SSH

40. Secure Shell

SSH supports secure remote command-line administration.

Use cases include:

• Linux administration;
• network-device management;
• secure tunneling.

41. SSH Security

Protect:

• administrative credentials;
• private SSH keys;
• authorized-key lists;
• server configurations.

42. Avoid Unnecessary Direct Exposure

Instead of:

INTERNET ─────► EVERY SERVER : SSH

prefer controlled architectures such as:

INTERNET

   │

   ▼

SECURE ADMIN GATEWAY

   │

   ▼

AUTHORIZED INTERNAL SERVER

Part XVI — Remote Desktop

43. RDP

Remote Desktop Protocol supports remote graphical access to Windows systems.

It can be operationally useful but should not normally be broadly exposed without appropriate protections.

44. RDP Protections

Consider:

• MFA;
• VPN or controlled access gateway;
• source restrictions;
• patching;
• logging;
• account lockout;
• session monitoring.

CISA recommends limiting RDP exposure and, when RDP is required, using measures such as MFA, logging, and restricting unnecessary remote desktop exposure.

Part XVII — Bastion Host

45. Bastion Host

A bastion host is a specially hardened system positioned to provide controlled access to more sensitive resources.

REMOTE ADMIN

     │

     ▼

BASTION HOST

     │

     ▼

INTERNAL ADMIN TARGETS

46. Harden More Aggressively

Because the bastion is exposed or highly trusted:

• minimize software;
• restrict users;
• monitor heavily;
• patch promptly.

Part XVIII — Jump Server

47. Jump Server

A jump server provides an intermediary administrative point between administrators and target systems.

ADMIN

  │

  ▼

JUMP SERVER

  │

  ├── SERVER A

  ├── SERVER B

  └── NETWORK DEVICE

48. Benefit

It creates a chokepoint for:

• authentication;
• logging;
• session control;
• network segmentation.

Part XIX — Privileged Access Workstation

49. PAW

A Privileged Access Workstation is a hardened endpoint dedicated to administrative activity.

The principle is:

Do not perform high-risk browsing, email, and privileged administration from the same unrestricted workstation.

50. Separation

NORMAL WORKSTATION

Email / Web / Office



          ≠



PRIVILEGED WORKSTATION

Administrative activity

Part XX — Privileged Session Monitoring

51. Monitor Administrative Sessions

High-value remote administration may justify:

• command logging;
• session recording;
• activity monitoring.

52. Purpose

This provides:

• accountability;
• incident evidence;
• misuse detection.

Part XXI — Time-Limited Privilege

53. Persistent Access Is Riskier

Vendor or administrator access does not necessarily need to remain active 24/7.

Instead:

REQUEST ACCESS

     │

     ▼

APPROVAL

     │

     ▼

TEMPORARY PRIVILEGE

     │

     ▼

TASK COMPLETE

     │

     ▼

ACCESS EXPIRES

54. Just-in-Time Access

JIT access reduces the time during which privileged authorization exists.

This limits opportunity for:

• credential theft;
• dormant account abuse.

Part XXII — Voice Communications

55. Voice Is Data

Modern enterprise voice often travels through IP networks.

Therefore voice communications can face:

• interception;
• impersonation;
• denial of service;
• unauthorized call routing.

Part XXIII — VoIP

56. Voice over IP

VoIP converts voice into network communication.

PHONE

  │

  ▼

VOICE SIGNAL

  │

  ▼

IP PACKETS

  │

  ▼

NETWORK

  │

  ▼

REMOTE PHONE

57. Two Broad Components

VoIP systems commonly involve:

• signaling;
• media.

Signaling establishes/manages calls.

Media carries the actual audio.

Part XXIV — SIP

58. Session Initiation Protocol

SIP is commonly associated with establishing, modifying, and terminating multimedia communication sessions.

At CISSP level:

Think call/session signaling.

59. Signaling Risk

Attackers may attempt:

• unauthorized registration;
• impersonation;
• call redirection;
• denial of service.

Part XXV — Voice Media Protection

60. Media Confidentiality

Voice traffic may require encryption where confidentiality is important.

Otherwise:

A network attacker capable of capturing media traffic may potentially listen to conversations.

61. Separate Signaling and Media Risks

Protecting signaling does not necessarily mean:

the media itself is encrypted.

Both paths must be evaluated.

Part XXVI — VoIP Availability

62. Convergence Creates Dependency

Traditional phones and data networks may have been separate.

VoIP converges them.

NETWORK FAILURE

      │

      ├── DATA OUTAGE

      └── VOICE OUTAGE

63. Emergency Planning

Voice infrastructure may require:

• redundancy;
• QoS;
• backup power;
• alternate communications.

Part XXVII — Video Conferencing

64. Video Is Sensitive Communication

Video platforms may expose:

• conversations;
• screens;
• documents;
• participant identities;
• recordings.

65. Video Threats

Examples include:

• unauthorized meeting entry;
• stolen meeting links;
• screen-sharing abuse;
• exposed recordings;
• compromised room systems.

Part XXVIII — Meeting Authentication

66. Not Every Meeting Needs the Same Security

Public webinar:

intentionally broad access.

Executive acquisition discussion:

tightly controlled participants.

Controls should reflect information sensitivity.

67. Meeting Security

Possible controls include:

• authenticated users;
• meeting passwords/passcodes;
• waiting rooms;
• host approval;
• participant restrictions.

Part XXIX — Screen Sharing

68. Screen Sharing Can Leak Information

Users may accidentally display:

• email;
• credentials;
• notifications;
• sensitive applications.

69. Reduce Exposure

Before sharing:

• close unnecessary applications;
• disable sensitive notifications;
• share specific windows where practical.

Part XXX — Meeting Recordings

70. Recording Creates a New Information Asset

A recording may contain:

• audio;
• video;
• chat;
• shared presentations.

71. Recording Lifecycle

RECORD

  │

  ▼

STORE

  │

  ▼

ACCESS CONTROL

  │

  ▼

RETENTION

  │

  ▼

DELETE / ARCHIVE

Treat recordings according to:

• classification;
• retention;
• privacy requirements.

Part XXXI — Collaboration Platforms

72. Collaboration Includes More Than Meetings

Platforms may support:

• messaging;
• file sharing;
• screen sharing;
• document collaboration;
• third-party integrations.

Each creates additional attack surfaces.

73. Collaboration Security Questions

Ask:

• Who can join?
• Who can invite guests?
• Who can share files?
• How is data retained?
• Which external applications can integrate?
• Are sessions logged?

Part XXXII — Conference and Collaboration Rooms

74. Room Systems Are Endpoints

Modern conference rooms may contain:

• computers;
• cameras;
• microphones;
• wireless interfaces;
• cloud accounts.

Therefore:

A conference room can be a network-connected endpoint.

75. Room-System Security

Protect:

• administrative credentials;
• firmware;
• physical access;
• meeting accounts;
• network segmentation.

76. Privacy Risk

A compromised room system could potentially expose:

• conversations;
• video;
• shared screens.

Part XXXIII — Data Communications

77. Data Communication Paths

Organizations may exchange data through:

• Internet tunnels;
• private circuits;
• cloud connections;
• carrier networks;
• satellite networks.

The channel should provide protection appropriate to the information risk.

Part XXXIV — Private Circuit

78. Private Does Not Automatically Mean Secure

A carrier-provided private circuit may reduce exposure compared with ordinary Internet routing.

But confidentiality requirements may still justify:

encryption.

79. CISSP Principle

Do not confuse:

Private path

with:

Cryptographically protected path.

Part XXXV — Carrier Networks

80. Telecommunications Providers

Carriers may transport:

• Internet;
• voice;
• private WAN traffic;
• mobile connectivity.

Dependence on a carrier creates third-party risk.

81. Carrier Questions

Ask:

• What availability is guaranteed?
• What security controls exist?
• What redundancy exists?
• How are incidents communicated?
• Are alternate carriers available?

Part XXXVI — Backhaul Networks

82. Backhaul

A backhaul network connects an edge, branch, wireless site, or remote system back toward a core network or service.

Conceptually:

REMOTE SITE

    │

    ▼

ACCESS NETWORK

    │

    ▼

BACKHAUL

    │

    ▼

CORE NETWORK

83. Security Importance

If backhaul fails:

the remote site may lose connectivity even though its local equipment still operates.

84. Backhaul Security

Consider:

• encryption;
• redundancy;
• carrier diversity;
• route diversity;
• monitoring.

Part XXXVII — Redundant Communications

85. Multiple Paths

SITE

 │ \

 │  \

FIBER 5G

 │     │

 └─────┘

    │

 CORE

A backup path using a different technology can improve resilience.

86. Common Failure Still Matters

Two fiber circuits may both use:

the same physical trench.

True resilience requires understanding actual dependencies.

Part XXXVIII — Satellite Communication

87. Satellite Links

Satellite communication may support:

• remote communities;
• maritime operations;
• disaster recovery;
• remote infrastructure;
• military/business operations.

The current CISSP outline explicitly identifies satellite communication under Domain 4.3.

88. Satellite Architecture

REMOTE TERMINAL

      │

      ▼

   UPLINK

      │

      ▼

  SATELLITE

      │

      ▼

  DOWNLINK

      │

      ▼

GROUND STATION

      │

      ▼

CORE NETWORK

89. Satellite Security Concerns

Consider:

• confidentiality;
• authentication;
• ground-station security;
• terminal security;
• availability;
• interference;
• provider trust.

NIST's Hybrid Satellite Network profile emphasizes managing cybersecurity across interfaces among independently owned and operated satellite components with potentially different assurance levels.

90. Ground Infrastructure Matters

Satellite security is not only about:

the spacecraft.

Ground systems, networks, applications, and terminals also need protection.

NIST's commercial satellite guidance emphasizes cybersecurity risk management across the supporting operational environment.

Part XXXIX — Satellite Latency

91. Performance Affects Security Design

Some satellite paths have higher latency than terrestrial connections.

This may influence:

• application behavior;
• timeouts;
• authentication protocols;
• interactive remote administration.

Part XL — Third-Party Connectivity

92. What Is Third-Party Connectivity?

Third-party connectivity allows an external organization to access systems or exchange information.

Examples:

• supplier VPN;
• MSP remote management;
• banking connection;
• partner API;
• hardware vendor remote support.

93. Third Party = New Trust Boundary

YOUR ORGANIZATION

      │

      ▼

SECURITY GATEWAY

      │

════ TRUST BOUNDARY ════

      │

      ▼

THIRD PARTY

Part XLI — Third-Party Principle

94. External Access Should Not Equal Internal Trust

A vendor with access to one server should not automatically receive access to:

• every server;
• backups;
• identity systems;
• security tools.

95. Least Privilege

VENDOR

  │

  ▼

ONLY REQUIRED SYSTEM

  │

  X

OTHER SYSTEMS

Part XLII — Segment Third Parties

96. Dedicated Vendor Zone

VENDOR

  │

  ▼

REMOTE ACCESS GATEWAY

  │

  ▼

VENDOR ACCESS ZONE

  │

  ▼

AUTHORIZED TARGET



       X



GENERAL INTERNAL NETWORK

97. Benefits

Segmentation can reduce:

• lateral movement;
• blast radius;
• unauthorized discovery.

Part XLIII — Third-Party MFA

98. Suppliers Need Strong Authentication Too

Do not weaken controls because:

“They are the vendor.”

Third-party privileged connections can be especially attractive to attackers.

Part XLIV — Vendor Accounts

99. Individual Accounts

Poor:

vendoradmin / shared among six technicians.

Better:

unique attributable identities where feasible.

100. Accountability

Unique accounts support:

• logging;
• revocation;
• investigation.

Part XLV — Temporary Vendor Access

101. Avoid Permanent Access When Unnecessary

SUPPORT REQUEST

      │

      ▼

APPROVAL

      │

      ▼

ACCOUNT ENABLED

      │

      ▼

MAINTENANCE SESSION

      │

      ▼

ACCESS DISABLED

CISA guidance for third-party access recommends least privilege and deactivation of third-party connections after the required work is completed.

Part XLVI — Hardware Support Connectivity

102. Support Modems and Remote Appliances

Some hardware may include vendor remote-support capability.

These connections can become:

hidden alternate entrances.

103. Questions to Ask

• Is remote access actually required?
• Can it be disabled?
• Who initiates the session?
• Is MFA used?
• Is access logged?
• Which systems can be reached?

Part XLVII — Remote Monitoring and Management Tools

104. RMM

Remote Monitoring and Management tools can provide powerful administrative capability.

Attackers also abuse legitimate remote-management tools.

CISA recommends inventorying and controlling authorized RMM software, monitoring its use, and requiring approved remote-access solutions.

105. Allow Only Authorized Tools

Organizations should know:

• which remote tools are approved;
• who can use them;
• which systems they can reach.

Part XLVIII — Vendor Session Monitoring

106. Privileged Third-Party Sessions

For sensitive systems, consider:

• session recording;
• command logging;
• real-time monitoring.

107. Why?

If a vendor changes:

• a firewall rule;
• database configuration;
• firmware;

the organization should maintain accountability.

Part XLIX — Third-Party Endpoint Risk

108. Vendor Device

A vendor may authenticate correctly using:

an infected laptop.

Therefore third-party access may require:

• managed jump environment;
• VDI;
• controlled support workstation;
• posture checking.

Part L — Virtual Desktop / Controlled Workspace

109. Keep Sensitive Data Inside

A virtual desktop can allow a remote user to interact with enterprise applications while reducing direct transfer of information to the external endpoint.

REMOTE DEVICE

     │

     ▼

SECURE SESSION

     │

     ▼

VIRTUAL DESKTOP

     │

     ▼

INTERNAL APPLICATIONS

110. Not Absolute Protection

Screenshots, compromised endpoints, and user actions still matter.

Part LI — Third-Party Information Exchanges

111. Secure Information Exchange

NIST SP 800-47 Rev. 1 emphasizes protecting exchanged information before, during, and after an exchange, based on risk.

112. Exchange Lifecycle

IDENTIFY EXCHANGE

      │

      ▼

ASSESS RISK

      │

      ▼

DEFINE PROTECTION

      │

      ▼

ESTABLISH AGREEMENT

      │

      ▼

IMPLEMENT CONNECTION

      │

      ▼

MONITOR

      │

      ▼

TERMINATE WHEN NO LONGER NEEDED

Part LII — Information Exchange Agreements

113. Agreement Purpose

An information-exchange agreement can define:

• protection requirements;
• organizational responsibilities;
• permitted information;
• incident responsibilities.

NIST defines an information exchange agreement as documenting protection requirements and responsibilities for information exchanged outside system authorization boundaries.

114. Contract Does Not Replace Technical Controls

A contract may say:

“Vendor shall protect the data.”

Technical controls must still enforce appropriate:

• authentication;
• encryption;
• access limits;
• monitoring.

Part LIII — SLA

115. Service-Level Agreement

An SLA can define measurable service expectations.

Examples:

• uptime;
• response time;
• support availability;
• incident notification.

116. SLA ≠ Security Guarantee

An SLA documents expectations.

It does not eliminate:

• vulnerabilities;
• threats;
• operational risk.

Part LIV — Telecom Provider Risk

117. Carrier Dependency

If one telecom provider supports:

• Internet;
• voice;
• backup connection;

the organization may have concentration risk.

118. Carrier Diversity

For critical communications, consider:

• alternate provider;
• alternate technology;
• alternate physical route.

Part LV — Connection Approval

119. Do Not Allow Ad Hoc Third-Party Connections

Before establishing external connectivity:

• identify business need;
• identify systems/data;
• assess risk;
• define controls;
• authorize the connection.

Part LVI — Connection Inventory

120. Know Every External Connection

Maintain awareness of:

• partners;
• carriers;
• cloud connections;
• vendor VPNs;
• remote-support pathways.

Unknown connections are difficult to protect.

Part LVII — Third-Party Connection Monitoring

121. Monitor Continuously

Watch for:

• unusual login times;
• excessive data transfer;
• access beyond assigned systems;
• failed authentication;
• configuration changes.

Part LVIII — Connection Termination

122. Third-Party Access Must End

When the:

• contract ends;
• support task ends;
• vendor employee leaves;
• system is replaced;

access should be reviewed or removed.

123. Termination Flow

RELATIONSHIP ENDS

      │

      ▼

DISABLE ACCOUNTS

      │

      ▼

REVOKE CERTIFICATES / TOKENS

      │

      ▼

REMOVE VPN / FIREWALL RULES

      │

      ▼

DELETE UNUSED TRUST

      │

      ▼

VERIFY

Part LIX — Dormant Access

124. Forgotten Vendor VPN

A vendor VPN that has not been used for two years may still provide:

an active attack path.

Lifecycle review matters.

Part LX — Secure Communication Availability

125. Confidentiality Is Not the Only Goal

A perfectly encrypted communication system is useless if:

nobody can connect during an emergency.

Secure communications also need:

• redundancy;
• capacity;
• resilience.

Part LXI — Communication Failover

126. Example

PRIMARY FIBER

      │

      X

      │

      ▼

5G / SATELLITE BACKUP

      │

      ▼

CRITICAL COMMUNICATION CONTINUES

Part LXII — Diverse Communication Technologies

127. Technology Diversity

A backup path using a different transmission technology can reduce shared failures.

Example:

• primary fiber;
• secondary cellular;
• emergency satellite.

Part LXIII — Secure Channel Monitoring

128. Encryption Reduces Visibility

Encryption protects confidentiality.

It can also hide:

malicious activity

from intermediate monitoring systems.

129. Architectural Decision

Organizations may place monitoring:

• before encryption;
• after decryption;
• at endpoints;
• at gateways.

The objective is to balance:

• privacy;
• confidentiality;
• threat detection.

Part LXIV — Logging

130. Remote-Access Logs

Useful records may include:

• user;
• device;
• source;
• start time;
• end time;
• destination resource;
• authentication result.

131. Third-Party Logs

For vendor activity, logs can support:

• accountability;
• contractual review;
• incident investigation.

Part LXV — Session Timeout

132. Idle Sessions

Long-lived unused sessions can increase risk.

Session policies may include:

• idle timeout;
• maximum duration;
• reauthentication.

Part LXVI — Reauthentication

133. Trust Can Change

A session authenticated at 8:00 AM should not necessarily receive indefinite trust.

Higher-risk operations may justify:

• step-up authentication;
• revalidation.

Part LXVII — Secure File Exchange

134. File Transfer Is a Communication Channel

Organizations may exchange files using:

• secure transfer services;
• collaboration platforms;
• managed portals.

Controls should consider:

• encryption;
• malware scanning;
• recipient authorization;
• retention.

Part LXVIII — Data Loss Risk

135. Outbound Communication

Remote access and third-party connectivity create egress paths.

Monitor for:

• excessive downloads;
• unusual transfer destinations;
• unauthorized copying.

Part LXIX — Current 5G Context

136. Cellular Security Is Evolving

Organizations increasingly use 4G/5G for:

• remote sites;
• backup connectivity;
• IoT;
• mobile users.

NIST published 5G Network Security Design Principles in March 2026, emphasizing isolation among data-plane, control-plane, and operations/maintenance traffic in 5G environments.

For CISSP purposes:

Treat cellular links as communication channels that still require risk-based identity, segmentation, management, and application security.

Part LXX — SierraTec Secure CHANNEL Model

137. CHANNEL Framework

Use CHANNEL when evaluating secure communication questions.

C — Confirm Identity

Who or what is connecting?

H — Harden the Endpoint

Is the communicating device trustworthy?

A — Authorize Only What Is Needed

Apply least privilege.

N — Network-Segment the Connection

Restrict the blast radius.

N — Negotiate Secure Protection

Use appropriate secure protocols and encryption.

E — Examine and Log Activity

Monitor sessions and anomalies.

L — Limit Duration and Lifecycle

Expire access when it is no longer required.

138. CHANNEL Diagram

C

CONFIRM IDENTITY

      │

      ▼

H

HARDEN ENDPOINT

      │

      ▼

A

AUTHORIZE

      │

      ▼

N

NETWORK SEGMENT

      │

      ▼

N

NEGOTIATE PROTECTION

      │

      ▼

E

EXAMINE / LOG

      │

      ▼

L

LIMIT LIFECYCLE

Part LXXI — Secure Remote-Access Architecture

139. Integrated Model

                    REMOTE USER

                         │

                         ▼

                 UNTRUSTED NETWORK

                         │

                         ▼

                 ACCESS GATEWAY

                         │

           ┌─────────────┼─────────────┐

           ▼             ▼             ▼

       IDENTITY       DEVICE       CONTEXT

           │             │             │

           └─────────────┼─────────────┘

                         ▼

                  POLICY DECISION

                         │

                         ▼

                 LEAST-PRIVILEGE

                     SESSION

                         │

                         ▼

                 AUTHORIZED RESOURCE

                         │

                         ▼

                    MONITORING

Part LXXII — Secure Vendor Architecture

140. Vendor Connectivity

VENDOR TECHNICIAN

       │

       ▼

MFA + AUTHORIZATION

       │

       ▼

VENDOR ACCESS GATEWAY

       │

       ▼

SESSION MONITORING

       │

       ▼

JUMP SERVER

       │

       ▼

AUTHORIZED DEVICE

       │

       X

OTHER ENTERPRISE SYSTEMS

Part LXXIII — Worked CISSP Scenarios

141. Scenario 1 — Remote Employee

An employee requires access to a sensitive finance application from home.

Which design is BEST?

A. Provide unrestricted Internet access directly to the finance server.

B. Use strongly authenticated secure remote access that limits the employee to required resources.

C. Allow Telnet directly from the Internet.

D. Share the finance administrator account.

Correct Answer

B

142. Scenario 2 — VPN Authentication

A company uses a strongly encrypted VPN but users authenticate with passwords that are frequently phished.

What is the MOST important improvement?

A. Add stronger user authentication such as MFA.

B. Increase monitor size.

C. Remove encryption.

D. Disable logging.

Correct Answer

A

Encryption does not compensate for weak identity controls.

143. Scenario 3 — Split Tunnel

Security wants all remote web traffic inspected through corporate controls.

Which configuration BEST supports this goal?

A. Full tunneling.

B. Split tunneling for all Internet traffic.

C. No VPN.

D. Public Telnet.

Correct Answer

A

144. Scenario 4 — Split-Tunnel Tradeoff

Users experience severe latency because all cloud collaboration traffic crosses a distant corporate VPN gateway.

What should the architect do?

A. Evaluate risk-based split tunneling or modern resource-specific access rather than assuming one design is always required.

B. Disable authentication.

C. Remove all endpoint protection.

D. Use Telnet.

Correct Answer

A

145. Scenario 5 — Remote Administration

Administrators currently connect directly from home computers to internal servers.

What is the BEST improvement?

A. Use managed administrative endpoints and controlled access through a privileged gateway/jump environment.

B. Open additional public administrative ports.

C. Share an administrator password.

D. Disable session logging.

Correct Answer

A

146. Scenario 6 — RDP

A Windows server exposes RDP directly to the public Internet.

Which recommendation is BEST?

A. Restrict remote desktop behind controlled secure access, require strong authentication, and monitor its use.

B. Remove all passwords.

C. Open RDP to every source.

D. Disable patching.

Correct Answer

A

CISA warns that exposed and poorly secured remote services are frequently abused by attackers.

147. Scenario 7 — Vendor Support

A hardware vendor requires access to one storage appliance for three hours.

What is the BEST access model?

A. Permanent enterprise VPN access.

B. Time-limited, monitored, least-privilege access to the specific system.

C. Shared domain administrator account.

D. Unrestricted internal access.

Correct Answer

B

148. Scenario 8 — Partner Access

A business partner requires database information for one application.

What should the organization do FIRST?

A. Identify the exchange requirements, data sensitivity, and necessary protection before establishing connectivity.

B. Give the partner internal network access.

C. Disable monitoring.

D. Share a privileged account.

Correct Answer

A

NIST SP 800-47 Rev. 1 recommends identifying information exchanges and establishing risk-based protections before, during, and after the exchange.

149. Scenario 9 — Voice

A company encrypts VoIP signaling but sends voice media unprotected.

What is the PRIMARY concern?

A. Conversations may still be intercepted through the media path.

B. Signaling encryption automatically protects everything.

C. Voice does not require confidentiality.

D. VLANs provide cryptographic confidentiality.

Correct Answer

A

150. Scenario 10 — Collaboration

An executive meeting contains confidential merger information.

Which practice is BEST?

A. Require appropriate participant controls, protect recordings, and restrict sharing.

B. Publish the meeting URL publicly.

C. Allow anonymous participants automatically.

D. Store recordings without access controls.

Correct Answer

A

Part LXXIV — Additional Scenarios

151. Scenario 11 — Backhaul

A remote operation depends on one telecommunications backhaul link.

What is the PRIMARY availability concern?

A. The backhaul is a single point of failure.

B. Encryption is too strong.

C. The site has too many users.

D. The satellite has a MAC address.

Correct Answer

A

152. Scenario 12 — Carrier Diversity

Two WAN circuits use different providers, but both traverse the same bridge.

What is the PRIMARY concern?

A. Common physical failure.

B. Excessive provider diversity.

C. Too much encryption.

D. Authentication latency.

Correct Answer

A

153. Scenario 13 — Satellite

A remote site uses satellite connectivity.

Which consideration is MOST appropriate?

A. Evaluate terminal, ground infrastructure, provider trust, encryption, latency, and availability.

B. Assume satellite traffic is naturally confidential.

C. Treat the satellite as the only component requiring security.

D. Disable endpoint authentication.

Correct Answer

A

154. Scenario 14 — Vendor Account

A vendor completed a maintenance project four months ago, but its VPN account is still active.

What should occur?

A. Disable the unnecessary account and review the connection lifecycle.

B. Leave it indefinitely.

C. Give it more privileges.

D. Remove MFA.

Correct Answer

A

155. Scenario 15 — Third-Party Device

A supplier has valid credentials but uses an unmanaged laptop.

What is the BEST concern?

A. User identity is valid, but endpoint trust has not been established.

B. Valid passwords guarantee device security.

C. Encryption makes device posture irrelevant.

D. The supplier should automatically receive administrator access.

Correct Answer

A

156. Scenario 16 — Conference Room

A network-connected conference-room system is still running unsupported firmware.

What is the BEST response?

A. Treat it as an endpoint, assess risk, patch/replace it, and appropriately segment it.

B. Ignore it because it is only a camera.

C. Give it unrestricted internal access.

D. Remove authentication.

Correct Answer

A

157. Scenario 17 — Vendor Monitoring

A third-party engineer performs privileged database maintenance.

Which control BEST supports accountability?

A. Individual identity plus privileged-session logging/recording.

B. Shared vendor password.

C. No logs.

D. Anonymous access.

Correct Answer

A

158. Scenario 18 — RMM

Security discovers several unauthorized remote-management tools on employee systems.

What is the BEST action?

A. Inventory, restrict, and monitor approved remote-management software while investigating unauthorized installations.

B. Ignore them because remote-management software is legitimate.

C. Permit every remote-support product.

D. Disable EDR.

Correct Answer

A

CISA specifically recommends auditing remote-access/RMM tools and restricting use to authorized solutions.

Part LXXV — Common CISSP Exam Traps

159. Trap — VPN Means Trusted

No.

VPN means:

Protected communication path.

Authorization and endpoint trust remain separate.

160. Trap — Encryption Solves Identity

No.

An encrypted connection to an attacker is still an attacker connection.

161. Trap — Remote User Needs Full Network Access

Prefer:

the least access required.

162. Trap — Split Tunneling Is Always Wrong

It is a risk/design tradeoff.

Evaluate:

• business need;
• endpoint security;
• inspection requirements.

163. Trap — Full Tunneling Is Always Best

Full tunneling improves centralized visibility but may affect:

• bandwidth;
• latency;
• performance.

164. Trap — ZTNA Is Just Another VPN

Zero Trust is broader and resource-centric.

It removes implicit trust based only on network location.

165. Trap — RDP Is Automatically Insecure

RDP can be used securely when:

• appropriately protected;
• patched;
• authenticated;
• restricted;
• monitored.

Direct uncontrolled exposure is the larger concern.

166. Trap — Bastion Host Does Not Need Hardening

A bastion host is highly security-sensitive precisely because many privileged connections may pass through it.

167. Trap — VoIP Is Only a Telephone Issue

VoIP is network communication and requires:

• confidentiality;
• availability;
• access control.

168. Trap — Securing SIP Means Voice Is Encrypted

Signaling and media are separate considerations.

169. Trap — Meeting Passcode Protects the Recording

The recording becomes a separate information asset after the meeting.

170. Trap — Private Circuit Means Encryption Is Unnecessary

Private transport reduces certain exposure but does not automatically provide cryptographic confidentiality.

171. Trap — Satellite Is Automatically Secure Because It Is Difficult to Reach

Satellite systems contain:

• terminals;
• ground stations;
• networks;
• provider infrastructure.

All create attack surfaces.

172. Trap — Vendor Is Trusted Because There Is a Contract

Contracts establish obligations.

Technical controls enforce access.

173. Trap — Third Parties Should Use Shared Accounts

Shared accounts reduce accountability.

174. Trap — Vendor Access Can Remain Active for Convenience

Inactive third-party access is unnecessary attack surface.

175. Trap — Telecom Provider Owns the Risk

Outsourcing transport does not eliminate the organization's responsibility to manage business risk.

Part LXXVI — Knowledge Check

176. Question 1

What is the PRIMARY purpose of a secure communication channel?

A. Provide required protection for information and communication across a connection.

B. Remove identity requirements.

C. Trust all endpoints.

D. Eliminate all business risk.

Correct Answer

A

177. Question 2

Which technology creates a protected logical connection across an untrusted network?

A. VPN.

B. Hub.

C. Patch panel.

D. UPS.

Correct Answer

A

178. Question 3

Which VPN type commonly connects an individual remote device to an enterprise network?

A. Remote-access/client VPN.

B. Site-to-site only.

C. RAID.

D. VLAN.

Correct Answer

A

179. Question 4

Which configuration routes most applicable client traffic through the enterprise VPN?

A. Full tunneling.

B. Split tunneling.

C. Anycast.

D. Multicast.

Correct Answer

A

180. Question 5

What is the main distinction of split tunneling?

A. Some traffic uses the enterprise tunnel while other traffic uses a direct path.

B. Two passwords are used.

C. Two VPN gateways must always be active.

D. Traffic is never encrypted.

Correct Answer

A

181. Question 6

What is MOST important in addition to VPN encryption?

A. Strong authentication and authorization.

B. Screen resolution.

C. Hardware color.

D. Broadcast addressing.

Correct Answer

A

182. Question 7

What is the central Zero Trust principle?

A. Do not grant implicit trust solely from network location.

B. Trust all internal systems.

C. Eliminate authentication.

D. Use one large internal network.

Correct Answer

A

183. Question 8

Which protocol is commonly preferred for secure command-line administration?

A. SSH.

B. Telnet.

C. HTTP.

D. FTP.

Correct Answer

A

184. Question 9

What is a jump server?

A. Controlled intermediary for administrative access.

B. Backup generator.

C. Public DNS server.

D. Network cable.

Correct Answer

A

185. Question 10

What is a primary purpose of a Privileged Access Workstation?

A. Separate high-risk administrative activity from ordinary user activity.

B. Replace network segmentation.

C. Store public websites.

D. Provide guest Wi-Fi.

Correct Answer

A

186. Question 11

What does SIP primarily relate to?

A. Multimedia/voice-session signaling.

B. Disk encryption.

C. RAID.

D. File sanitization.

Correct Answer

A

187. Question 12

What should happen to confidential meeting recordings?

A. Protect them according to their information classification and retention requirements.

B. Publish them automatically.

C. Treat them as non-data.

D. Keep them forever.

Correct Answer

A

188. Question 13

What is backhaul?

A. Communication path connecting an edge or remote environment toward the core.

B. Password hashing.

C. Local disk storage.

D. Digital certificate.

Correct Answer

A

189. Question 14

Which is a major satellite-communication security consideration?

A. Protecting terminals, ground infrastructure, channels, and provider interfaces.

B. Assuming radio transmission is confidential.

C. Ignoring availability.

D. Removing authentication.

Correct Answer

A

190. Question 15

How should third-party access generally be granted?

A. According to least privilege.

B. As full administrator by default.

C. Without monitoring.

D. Permanently.

Correct Answer

A

191. Question 16

Why should vendor access often be time limited?

A. To reduce unnecessary exposure after the task ends.

B. To increase credential sharing.

C. To disable accountability.

D. To avoid authentication.

Correct Answer

A

192. Question 17

What should an information-exchange agreement document?

A. Protection requirements and organizational responsibilities for exchanged information.

B. Passwords.

C. Encryption keys.

D. Firewall administrator credentials.

Correct Answer

A

193. Question 18

What is an important control for third-party privileged sessions?

A. Logging and monitoring.

B. Anonymous access.

C. Shared passwords only.

D. Disable auditing.

Correct Answer

A

194. Question 19

What should happen when vendor connectivity is no longer required?

A. Remove or disable the connection and associated credentials.

B. Keep it permanently.

C. Increase privileges.

D. Disable MFA.

Correct Answer

A

195. Question 20

Which statement is MOST accurate?

A. Secure communications require protection of identity, endpoint, channel, authorization, monitoring, and lifecycle.

B. Encryption alone solves every communication risk.

C. Private circuits require no risk analysis.

D. Vendors should automatically be trusted.

Correct Answer

A

Part LXXVII — Original CISSP-Style Practice Questions

196. Practice Question 1

A remote employee authenticates successfully, but endpoint security reports the laptop has been compromised.

What is the BEST response?

A. Restrict the session and initiate remediation rather than grant normal production access.

B. Grant access because the password was correct.

C. Disable endpoint monitoring.

D. Give administrator access.

Correct Answer

A

197. Practice Question 2

A vendor requires periodic access to one firewall but currently has unrestricted VPN access to the entire infrastructure network.

What is the BEST improvement?

A. Restrict the vendor to a controlled privileged path and only the firewall required.

B. Give the vendor domain-administrator rights.

C. Remove logging.

D. Allow anonymous access.

Correct Answer

A

198. Practice Question 3

A company secures remote access using a VPN but has no process to terminate former-contractor accounts.

What is the PRIMARY weakness?

A. Access lifecycle management.

B. Encryption.

C. Bandwidth.

D. Signal attenuation.

Correct Answer

A

199. Practice Question 4

An executive wants confidential collaboration sessions but allows anyone possessing the meeting link to join anonymously.

Which control should be improved FIRST?

A. Participant authentication and authorization.

B. Video resolution.

C. Microphone volume.

D. Screen size.

Correct Answer

A

200. Practice Question 5

A company has redundant WAN links from two carriers but both cables enter through the same underground conduit.

Which risk remains?

A. Common-mode physical failure.

B. Excessive redundancy.

C. Weak hashing.

D. Certificate expiration.

Correct Answer

A

201. Practice Question 6

An administrator wants to expose SSH directly from every server to the public Internet for convenience.

What is the BEST alternative?

A. Route privileged access through a hardened controlled administrative gateway or jump environment.

B. Use Telnet instead.

C. Share one root password.

D. Disable logging.

Correct Answer

A

202. Practice Question 7

A telecom provider advertises its MPLS/private network as secure, so management proposes removing application encryption for sensitive data.

What is the BEST response?

A. Evaluate confidentiality requirements independently of whether the transport network is private.

B. Private networks make encryption unnecessary in every case.

C. Public-key cryptography is prohibited on carrier networks.

D. Ignore data classification.

Correct Answer

A

203. Practice Question 8

A hardware-maintenance provider uses one account shared by all technicians.

What is the PRIMARY concern?

A. Lack of individual accountability.

B. Excessive confidentiality.

C. Too much segmentation.

D. High bandwidth.

Correct Answer

A

204. Practice Question 9

A remote-support tool is installed throughout the enterprise but the security team does not know who uses it or when.

What should happen FIRST?

A. Inventory and govern the remote-access capability and review associated access.

B. Ignore it because it is commercial software.

C. Disable security logging.

D. Publish access credentials.

Correct Answer

A

205. Practice Question 10

A supplier connection has not been used in eighteen months but remains configured through the enterprise firewall.

Which action is BEST?

A. Verify business need and remove the connection if no longer required.

B. Leave all historical connections permanently.

C. Expand its access.

D. Eliminate firewall monitoring.

Correct Answer

A

Part LXXVIII — Remote Access Memory Table

Part LXXIX — Communication Memory Table

Part LXXX — Third-Party Memory Table

Part LXXXI — Key Terms

Secure Communication Channel

Communication path protected according to required confidentiality, integrity, authentication, authorization, and availability needs.

Remote Access

Access to enterprise resources from outside the normal enterprise location or boundary.

Remote-Access Gateway

Controlled entry point for remote sessions.

VPN

Virtual Private Network.

Remote-Access VPN

VPN connecting an individual endpoint to an enterprise environment.

Site-to-Site VPN

VPN connecting two networks or sites.

Full Tunneling

Routing applicable traffic through the enterprise VPN.

Split Tunneling

Routing selected traffic through the VPN while other traffic uses direct connectivity.

ZTNA

Zero Trust Network Access; resource-focused access based on identity, device, policy, and context.

SSH

Secure Shell protocol used for secure remote administration.

RDP

Remote Desktop Protocol.

Bastion Host

Hardened system providing controlled access to protected environments.

Jump Server

Administrative intermediary used to reach protected systems.

PAW

Privileged Access Workstation.

Just-in-Time Access

Privilege activated only for a limited period when needed.

VoIP

Voice over Internet Protocol.

SIP

Session Initiation Protocol.

Collaboration Platform

Communication environment supporting conferencing, messaging, file sharing, and related functions.

Backhaul

Communication path connecting an edge or remote environment toward a central/core network.

Satellite Communication

Communication using satellite and associated terminal/ground infrastructure.

Third-Party Connectivity

Network or application access involving another organization.

RMM

Remote Monitoring and Management software.

Information Exchange Agreement

Agreement documenting protection requirements and responsibilities for information shared outside an organization's authorization boundary.

Session Monitoring

Observation and recording of communication or administrative activity for security/accountability.

Carrier Diversity

Use of multiple telecommunications providers or routes to improve resilience.

Common-Mode Failure

Single failure affecting multiple supposedly redundant communication paths.

CISSP Exam Focus

For secure-channel questions, think:

WHO?

 ↓

WHAT DEVICE?

 ↓

WHAT RESOURCE?

 ↓

WHAT CHANNEL?

 ↓

WHAT ENCRYPTION?

 ↓

WHAT AUTHORIZATION?

 ↓

WHAT MONITORING?

 ↓

WHEN DOES ACCESS END?

Remember these high-yield principles:

• Domain 4.3 explicitly covers collaboration, remote access, data communications, and third-party connectivity.
• Encryption is necessary for many remote channels but does not replace identity or authorization.
• Remote access should use strong authentication.
• Endpoint posture can matter as much as user identity.
• VPN access should be limited according to need.
• Full tunneling improves centralized visibility but increases network load.
• Split tunneling has performance advantages and security tradeoffs.
• Zero Trust removes implicit trust based only on physical or network location.
• ZTNA commonly focuses access on specific resources rather than broad network reachability.
• Remote administrative access deserves stronger protections than ordinary user access.
• Avoid unnecessarily exposing administrative protocols directly to the Internet.
• Use hardened jump/bastion architectures when appropriate.
• Privileged sessions should be attributable and monitored.
• Temporary privilege is usually safer than permanently enabled vendor access.
• VoIP signaling and media are different security considerations.
• Collaboration-room devices are network endpoints.
• Meeting recordings become information assets.
• A private carrier connection is not automatically equivalent to encryption.
• Backhaul availability can determine remote-site availability.
• Satellite security includes terminals, ground systems, interfaces, and provider relationships—not only the spacecraft.
• Third-party connections introduce additional trust boundaries.
• NIST recommends protecting exchanged information before, during, and after the exchange based on risk.
• Third-party access should use least privilege.
• Vendor access should normally be disabled when the business need ends.
• CISA recommends tightly controlling remote-management software and third-party remote connections because attackers frequently abuse such access pathways.

Lesson Summary

Lesson Sixteen completed the primary Communication and Network Security sequence by examining how communication should be protected when it crosses enterprise trust boundaries.

The current CISSP Domain 4.3 scope is:

VOICE / VIDEO / COLLABORATION

             │

        REMOTE ACCESS

             │

      DATA COMMUNICATION

             │

   THIRD-PARTY CONNECTIVITY

You learned that secure remote access is more than creating an encrypted VPN:

IDENTITY

   +

DEVICE

   +

SECURE CHANNEL

   +

AUTHORIZATION

   +

SEGMENTATION

   +

MONITORING

   =

SECURE REMOTE ACCESS

NIST's remote-access guidance similarly treats endpoint security and remote-access technology as interconnected requirements, particularly for employees, contractors, partners, vendors, and BYOD environments.

You examined:

• remote-access VPNs;
• site-to-site VPNs;
• IPsec;
• TLS-based remote access;
• full tunneling;
• split tunneling;
• MFA;
• device posture;
• Zero Trust Network Access.

NIST Zero Trust guidance emphasizes that neither network location nor device ownership alone should create implicit trust. Access should be based on authentication and authorization of subjects and devices before resource sessions are established.

You also examined secure administrative communication using:

• SSH;
• controlled RDP;
• bastion hosts;
• jump servers;
• privileged-access workstations;
• session monitoring;
• just-in-time access.

You learned that collaboration technologies themselves form security boundaries:

VOICE

VIDEO

CHAT

FILES

SCREEN SHARING

RECORDINGS

     │

     ▼

SENSITIVE INFORMATION CHANNELS

You then studied data communications including:

• carrier networks;
• backhaul;
• redundant paths;
• cellular links;
• satellite communication.

Finally, you applied the same principles to third parties.

NIST SP 800-47 Rev. 1 states that information exchanged between organizations should receive protection commensurate with risk before, during, and after the exchange.

The secure third-party lifecycle is therefore:

BUSINESS NEED

      ↓

RISK ASSESSMENT

      ↓

SECURITY AGREEMENT

      ↓

STRONG AUTHENTICATION

      ↓

LEAST-PRIVILEGE ACCESS

      ↓

SEGMENTATION

      ↓

MONITORING

      ↓

PERIODIC REVIEW

      ↓

TERMINATION

The central Lesson Sixteen principle is:

A communication channel is secure only when the organization protects not just the traffic, but also the identities, devices, authorization boundaries, endpoints, monitoring, availability, and complete lifecycle of the connection.

Exam Readiness Check

Before moving into Domain 5, make sure you can explain without reviewing:

• What makes a communication channel secure.
• Why encryption alone does not establish trust.
• What remote access is.
• The major risks of remote access.
• What a remote-access gateway does.
• What a remote-access/client VPN does.
• What a site-to-site VPN does.
• How IPsec supports VPNs.
• What full tunneling means.
• What split tunneling means.
• The advantages and risks of split tunneling.
• Why MFA is important for remote access.
• Why endpoint posture matters.
• What Zero Trust Network Access means.
• Why ZTNA is not simply another name for VPN.
• Why remote administrative access should be tightly controlled.
• What SSH is used for.
• Why RDP should not be indiscriminately exposed.
• What a bastion host is.
• What a jump server is.
• What a Privileged Access Workstation is.
• Why privileged sessions may require recording.
• What just-in-time access means.
• Why voice traffic should be treated as network data.
• What SIP does conceptually.
• Why VoIP signaling and media are separate security concerns.
• Why video meetings require access controls.
• Why screen sharing can expose sensitive information.
• Why recordings must be classified and protected.
• Why conference-room systems should be treated as endpoints.
• What backhaul means.
• Why backhaul requires resilience.
• Why private circuits do not automatically eliminate encryption requirements.
• Why carrier diversity matters.
• Why physical-path diversity also matters.
• Major satellite communication security concerns.
• Why ground infrastructure matters in satellite security.
• What third-party connectivity means.
• Why third parties introduce new trust boundaries.
• Why least privilege applies to vendors.
• Why third parties should be segmented.
• Why shared vendor accounts reduce accountability.
• Why vendor connections should often be temporary.
• Why remote-management software requires governance.
• What an information-exchange agreement does.
• Why contracts do not replace technical security controls.
• Why third-party connections must be inventoried and monitored.
• What should happen when the business need for a connection ends.

Coming Next

Lesson Seventeen: Identity and Access Management Foundations

Lesson Seventeen will begin CISSP Domain 5 — Identity and Access Management (IAM).

It will cover:

• identity concepts;
• subjects and objects;
• identification;
• authentication;
• authorization;
• accounting;
• accountability;
• physical access;
• logical access;
• information access;
• system access;
• device access;
• facility access;
• application access;
• service access;
• identity lifecycle;
• joiner/mover/leaver processes;
• account provisioning;
• deprovisioning;
• access reviews;
• groups;
• roles;
• permissions;
• entitlement management;
• least privilege;
• need to know;
• separation of duties;
• privileged accounts;
• service accounts;
• shared accounts;
• MFA;
• passwordless authentication;
• knowledge factors;
• possession factors;
• inherence factors;
• location and behavioral factors;
• biometrics;
• FAR;
• FRR;
• CER/EER;
• identity proofing;
• device identity;
• service identity;
• original IAM diagrams;
• knowledge checks;
• CISSP-style scenarios.

The central Lesson Seventeen question will be:

How should an organization establish identity, prove identity, authorize appropriate access, maintain accountability, and remove access when it is no longer required?

Publication and Independence Notice

This lesson is independently developed educational material for the SierraTec Secure CISSP Certification Preparation Course.

CISSP is administered by ISC2. SierraTec Secure's program is independent certification-preparation material and should not be represented as official ISC2 training unless separately authorized.

The primary scope was verified against the current ISC2 CISSP Examination Outline. Objective 4.3 currently includes voice/video/collaboration, remote access and network-administrative functions, data communications including backhaul and satellite, and third-party connectivity including telecommunications and hardware-support relationships.

Remote-access concepts were supplemented by NIST SP 800-46 Rev. 2. NIST continues to list Revision 2 as the final publication, while the proposed Revision 3 remains a preliminary draft effort; therefore this lesson uses Revision 2 for final NIST remote-access guidance and newer Zero Trust publications for modern architectural context.

Zero Trust concepts were aligned with NIST SP 800-207 and SP 800-207A.

Third-party information-exchange concepts were supplemented by final NIST SP 800-47 Rev. 1.

Satellite communication context was supplemented with NIST IR 8441 and NIST IR 8270.

The SierraTec Secure CHANNEL framework, diagrams, comparison tables, knowledge checks, scenarios, and practice questions are original educational content and are not actual, recalled, leaked, or official CISSP examination questions.