Remote Access - CompTIA A+ 220-1202 - 4.9 — Transcript
Full transcript
- 0:02If you've ever worked in a help desk,
- 0:03then you're probably very familiar with
- 0:05remote desktop connections. This is when
- 0:07you can share someone else's desktop
- 0:10while sitting at your desk. That user's
- 0:12desktop may be in the next room, the
- 0:15next building over, or the next country.
- 0:17You're able to make this connection
- 0:19using a number of different utilities.
- 0:21You might be using RDP, which is part of
- 0:23the Microsoft Remote Desktop Protocol.
- 0:26There are clients or applications you
- 0:28can run to connect to other RDP services
- 0:31in Mac OS, Linux, Windows, your mobile
- 0:34devices, and almost any other operating
- 0:37system. There's of course open- source
- 0:39options available for remote desktop
- 0:41using VNC. This is the virtual network
- 0:44computing. It uses a protocol known as
- 0:47RFB or remote frame buffer. There are
- 0:50also clients available on many different
- 0:52operating systems. If you're using VNC
- 0:54for your remote desktop connection,
- 0:57remote desktop enables any organization
- 0:59to support everyone in the field
- 1:01regardless of where they might be, but
- 1:04scammers love to use remote desktop as
- 1:06well. So, if you find that a third party
- 1:08is trying to connect to you using remote
- 1:10desktop, you might want to get a bit
- 1:12more information before allowing a third
- 1:14party access to your computer.
- 1:17One way to tell if someone has a remote
- 1:19desktop service running on their system
- 1:22is to check available open ports. The
- 1:24remote desktop service, of course, is
- 1:26waiting for someone to connect to that
- 1:29device to be able to control it. If
- 1:31someone has an open port of TCP port
- 1:343389,
- 1:35then they are most likely running a
- 1:37remote desktop service and someone with
- 1:40the correct credentials would be able to
- 1:42connect to this device and be able to
- 1:43control the desktop. Of course, someone
- 1:46might be running VNC or one of the many
- 1:48other third-party remote desktop
- 1:50solutions out there. They're usually
- 1:52just secured with a username and a
- 1:54password. This makes it very easy to
- 1:56perform a brute force attack. So, you
- 1:59might want to add additional
- 2:00authentication factors to keep anyone
- 2:02from connecting to your device from a
- 2:04remote location. Attackers love to take
- 2:07advantage of open ports for remote
- 2:09desktop and easy to find usernames and
- 2:11passwords because once they're on a
- 2:13system, it's all theirs as if they were
- 2:16sitting in front of the computer
- 2:17physically. They're able to go through
- 2:19all of your files. They're able to
- 2:21connect to other sites and they're able
- 2:23to perform whatever they'd like to do
- 2:25from your machine using remote desktop.
- 2:29If you have a mobile device or a laptop
- 2:31and you need to connect back to your
- 2:33corporate office across the internet,
- 2:35then you're probably very familiar with
- 2:37a VPN. This is a virtual private network
- 2:40and it encrypts all of the data going
- 2:42back and forth between you and the other
- 2:44device, even if you're going across a
- 2:46public network like the internet. From
- 2:48your device, you're connecting to a VPN
- 2:51concentrator. This is a centralized
- 2:53device. Usually, it's at your point of
- 2:55business and everyone who needs access
- 2:57to your company is going to use the VPN
- 2:59client on their computer to connect to
- 3:01the VPN concentrator at your corporate
- 3:04office. You may find that you have a
- 3:06single appliance or server that's
- 3:08configured as a VPN concentrator, but
- 3:10these days you often find VPN
- 3:12concentrators built into next generation
- 3:15firewalls. This gives you options as to
- 3:17how you'd like to deploy these VPN
- 3:19services. You can build your own
- 3:20softwarebased VPN or you can use an
- 3:23integrated hardwarebased VPN that may be
- 3:26part of your nextG firewall. Some VPN
- 3:28concentrators require that you install
- 3:30special software on your client machine.
- 3:33Other operating systems have builtin
- 3:35VPNs and you may be able to connect to
- 3:37the VPN concentrator using software
- 3:39that's already available in Windows,
- 3:41Linux, or Mac OS.
- 3:44Here's how a VPN works visually. You're
- 3:46the remote user at home that needs to
- 3:49access resources that are on your
- 3:51corporate network, but your only
- 3:52connection is through the internet, and
- 3:54you certainly don't want to send
- 3:55unencrypted information across that
- 3:57public network. So, you'll use VPN
- 4:00software on your remote device to
- 4:02encrypt all of the data sent across the
- 4:04internet. And on the other side, the
- 4:06device that is acting as your VPN
- 4:07concentrator will decrypt that
- 4:09information and send it into your
- 4:11corporate network. For this information
- 4:13to get back to you, we simply reverse
- 4:15this process. So information is sent
- 4:17from your corporate network. It hits the
- 4:19VPN concentrator where it is encrypted,
- 4:21sent across the internet, and it's
- 4:23decrypted on your local device at home.
- 4:26We rely on VPNs to encrypt and secure
- 4:28all of the data that we're sending
- 4:30across the network. This means that if
- 4:32someone's taking a packet capture or has
- 4:34some way to view the information that
- 4:36we're sending across the network would
- 4:37not be able to see any of the data since
- 4:40it's all encrypted over the network.
- 4:42When you're connecting to that
- 4:43concentrator, you're often asked for
- 4:45some type of authentication credentials.
- 4:48If you're only using a username and
- 4:49password, there is a potential that
- 4:51someone could perform a brute force
- 4:53attack to try to determine the best
- 4:55combination to gain access to that
- 4:57system. This means that we often have
- 4:59additional multiffactor authentication
- 5:01that we use during this login process.
- 5:04So we might provide a username, a
- 5:06password, and then an additional code
- 5:08that's provided to us from an app. This
- 5:10ensures that only people authorized are
- 5:12able to gain access to this virtual
- 5:14private network.
- 5:17As an administrator, there may be times
- 5:19when you need to connect to a remote
- 5:21device and be able to make a
- 5:22configuration change at the console of
- 5:25that device. In order to have a
- 5:27protected communication between your
- 5:29device and the remote device, you would
- 5:31probably use SSH or secure shell. Secure
- 5:35shell is designed for terminal
- 5:36communication like the one you see here,
- 5:38and it uses TCP port 22 in order to
- 5:42communicate. This looks and feels very
- 5:44similar to the older Tnet protocol which
- 5:46runs on TCP port 23, but all of the
- 5:49communication used by Tnet is sent in
- 5:52the clear across the network. If you
- 5:54want to have an encrypted connection to
- 5:56that remote device, you'll always want
- 5:58to use secure shell.
- 6:01There's a great deal of security built
- 6:03into SSH, which is why it's a great
- 6:05utility to use for connecting to that
- 6:07remote terminal. Since all of the SSH
- 6:10communication is sent and encrypted,
- 6:12there's no way for anyone to perform a
- 6:14packet capture and somehow determine
- 6:16what your username and password might
- 6:18be. You can enhance the use of SSH by
- 6:21adding additional authentication
- 6:22options. For example, SSH supports the
- 6:25use of public private key pairs to add
- 6:27additional authentication for connecting
- 6:29to that remote device. And as a best
- 6:32practice, it's probably a good idea to
- 6:34disable any type of remote access to
- 6:36certain usernames. For example, the root
- 6:39account on a Linux machine is the super
- 6:41user of that device, and you probably
- 6:44don't want people being able to log in
- 6:46as root by using SSH. Some organizations
- 6:49have completely removed all
- 6:51password-based authentication, and they
- 6:53require a certificate to be able to
- 6:55authenticate to these remote devices.
- 6:58You can enhance this by limiting who's
- 7:00able to connect to these remote devices
- 7:02based on an IP address. So, you might
- 7:04want to configure a filter or network
- 7:06firewall to be able to only allow access
- 7:10to or from certain IP address ranges.
- 7:14Many organizations have outsourced the
- 7:16monitoring and ongoing maintenance of
- 7:18their networks by using a managed
- 7:21service provider or MSP. The MSP will
- 7:24often use a tool known as an RMM in
- 7:27order to provide that monitoring. RMM
- 7:30stands for remote monitoring and
- 7:32management. And this provides a way for
- 7:34the MSP to be able to monitor and manage
- 7:37all of their customers from one single
- 7:39console. From this single console, your
- 7:42MSP can patch operating systems, log in
- 7:45remotely to a device, monitor for any
- 7:47security anomalies, and provide
- 7:49additional inventory of your hardware
- 7:52and software.
- 7:53Here's an example of an RMM that I've
- 7:56used. You can see on the left side that
- 7:58this MSP has six different companies
- 8:00that they can access. And right now
- 8:02we're looking at company 5 which has
- 8:03three different locations in HQ5, LA
- 8:06Office 5, and New York Office 5. You can
- 8:10see across those we're looking at the LA
- 8:12office right now. And the LA office has
- 8:14a file server, there's Karen's laptop,
- 8:16there's domain controllers and a file
- 8:18server. We can also see a status of how
- 8:20those devices are running. And we can
- 8:22get detailed information about the
- 8:24monitoring and ongoing performance of
- 8:27each individual device.
- 8:30This remote monitoring and management
- 8:32tool has access to many different
- 8:34customers from one single screen. This
- 8:36makes it very attractive to an attacker
- 8:38because once they get access to the RMM,
- 8:41they now have access to many different
- 8:43companies. This is why access to this
- 8:45console should be very tightly
- 8:47controlled and limited to only the
- 8:49authorized users. We might also want to
- 8:52require multiffactor authentication to
- 8:54anyone who logs into the RMM console.
- 8:57and we might want to perform ongoing
- 8:59auditing to make sure that we know
- 9:01exactly who's connecting to our RMM
- 9:03console.
- 9:06As our cloud infrastructures became
- 9:08larger and larger, we needed a better
- 9:10way to remotely connect and manage these
- 9:12virtual machines. We were able to
- 9:14provide that by using Spice. This is the
- 9:17simple protocol for independent
- 9:19computing environments. This allows us
- 9:21to view and control the remote desktop
- 9:24on a virtual machine using a very
- 9:26lightweight and easy to use protocol.
- 9:29This provides a seamless remote control
- 9:31solution across many different operating
- 9:34systems running in many different
- 9:36virtual machines. If you've ever used
- 9:38any type of remote control software,
- 9:40then running a Spice protocol
- 9:42application is going to be very similar.
- 9:44Spice excels by having very efficient
- 9:47graphics rendering and very fast
- 9:49response times. and you're able to
- 9:50integrate with that remote operating
- 9:52system by sharing the folder and
- 9:54clipboard between your device and the
- 9:56spice enabled virtual machine.
- 10:00When you run a script in Windows, you
- 10:02have to connect to that Windows machine,
- 10:04run the script, and then be able to see
- 10:06the results of that script on something
- 10:08like a remote desktop or remote terminal
- 10:11screen. But what if you could send that
- 10:13script to a third-party Windows device,
- 10:16have it run the script, and then have
- 10:18all the results of that script sent back
- 10:19to you without directly connecting to
- 10:22that remote device. You're able to do
- 10:24that by using Windows Remote Management
- 10:26or WinRM.
- 10:28WinRM is turned on by default on most
- 10:31Windows servers. So, all the
- 10:32administrator needs to do is send the
- 10:34script to that Windows server.
- 10:36Obviously, the administrator will need
- 10:38to authenticate to that remote device
- 10:40when they're sending the script to
- 10:42verify that the script is trusted. The
- 10:44script then runs on that remote server,
- 10:46and the resulting information is all
- 10:48sent back to the original screen to be
- 10:51able to evaluate what occurred during
- 10:53that script.
- 10:55I used Winrm on my local device to run a
- 10:58script on an external server. My local
- 11:01device is the NACO lab server and I'm
- 11:04connecting to a server that's elsewhere
- 11:05on the network called Atlantis Lab PC.
- 11:08I'm running a script that performs a get
- 11:10wmi object of all the Win32 services.
- 11:13So, this should tell me all the services
- 11:15running on that remote device. When I
- 11:18send this information over, it asks for
- 11:20authentication. I add my username and my
- 11:22password. And what I receive in return
- 11:24are the results of that script that have
- 11:26run on that remote server. I didn't have
- 11:29to perform a remote desktop to that
- 11:31device or interactively connect through
- 11:33a console or terminal. I simply used
- 11:35WinRM to run that script remotely.
- 11:40You might also find a number of
- 11:41thirdparty tools that provide a number
- 11:43of different remote management
- 11:44capabilities. For example, if you need
- 11:46to perform screen sharing, you can use
- 11:48Go to My PC, Team Viewer, or similar
- 11:51third-party utility. If you want to be
- 11:53able to video conference, there are many
- 11:55options available on the market. Two of
- 11:57the most popular are Zoom and Webex. You
- 12:00might also find tools that allow you to
- 12:02easily store and transfer files between
- 12:05systems. If you're using Dropbox,
- 12:07Box.com, or Google Drive, then you've
- 12:09taken advantage of some of this file
- 12:11synchronization technology. Or if you're
- 12:14performing ongoing desktop management of
- 12:16a system where you're monitoring and
- 12:18updating those systems, you might be
- 12:20using Citrix Endpoint Management or
- 12:22Manage Engine Desktop Central. All of
- 12:25these thirdparty utilities have
- 12:26advantages and disadvantages, but the
- 12:29key to all of them is making sure that
- 12:30we use appropriate security,
- 12:32multiffactor authentication, and limit
- 12:35access to only the people who are
- 12:37authorized.
About this transcript
This page contains the full transcript of Remote Access - CompTIA A+ 220-1202 - 4.9 by Professor Messer, generated from the public captions YouTube serves with the video. The transcript has 2,172 words across 339 segments, with the original timestamps preserved so you can click any line to jump to that moment in the embedded player.
What you can do with it
Use the transcript to take notes, quote the speaker, build a study guide, generate a summary with ChatGPT or Claude via the YouTube Summary tool, or export it as a timed subtitle file with YouTube to SRT. You can also re-open it in the transcriber to choose a caption track available on the video.
Free YouTube transcript tool
YouTube2Text is a free YouTube transcript generator — no signup, no daily limit. Paste any YouTube link and get the full transcript instantly, with timestamps, click-to-jump, caption language selection, AI prompts for ChatGPT, Claude, and Gemini, and exports to TXT, SRT, VTT, or Markdown.