YouTube2Text

Remote Access - CompTIA A+ 220-1202 - 4.9 — Transcript

by Professor Messer · 2,172 words · 339 segments · language en · Watch on YouTube

Full transcript

  1. 0:02If you've ever worked in a help desk,
  2. 0:03then you're probably very familiar with
  3. 0:05remote desktop connections. This is when
  4. 0:07you can share someone else's desktop
  5. 0:10while sitting at your desk. That user's
  6. 0:12desktop may be in the next room, the
  7. 0:15next building over, or the next country.
  8. 0:17You're able to make this connection
  9. 0:19using a number of different utilities.
  10. 0:21You might be using RDP, which is part of
  11. 0:23the Microsoft Remote Desktop Protocol.
  12. 0:26There are clients or applications you
  13. 0:28can run to connect to other RDP services
  14. 0:31in Mac OS, Linux, Windows, your mobile
  15. 0:34devices, and almost any other operating
  16. 0:37system. There's of course open- source
  17. 0:39options available for remote desktop
  18. 0:41using VNC. This is the virtual network
  19. 0:44computing. It uses a protocol known as
  20. 0:47RFB or remote frame buffer. There are
  21. 0:50also clients available on many different
  22. 0:52operating systems. If you're using VNC
  23. 0:54for your remote desktop connection,
  24. 0:57remote desktop enables any organization
  25. 0:59to support everyone in the field
  26. 1:01regardless of where they might be, but
  27. 1:04scammers love to use remote desktop as
  28. 1:06well. So, if you find that a third party
  29. 1:08is trying to connect to you using remote
  30. 1:10desktop, you might want to get a bit
  31. 1:12more information before allowing a third
  32. 1:14party access to your computer.
  33. 1:17One way to tell if someone has a remote
  34. 1:19desktop service running on their system
  35. 1:22is to check available open ports. The
  36. 1:24remote desktop service, of course, is
  37. 1:26waiting for someone to connect to that
  38. 1:29device to be able to control it. If
  39. 1:31someone has an open port of TCP port
  40. 1:343389,
  41. 1:35then they are most likely running a
  42. 1:37remote desktop service and someone with
  43. 1:40the correct credentials would be able to
  44. 1:42connect to this device and be able to
  45. 1:43control the desktop. Of course, someone
  46. 1:46might be running VNC or one of the many
  47. 1:48other third-party remote desktop
  48. 1:50solutions out there. They're usually
  49. 1:52just secured with a username and a
  50. 1:54password. This makes it very easy to
  51. 1:56perform a brute force attack. So, you
  52. 1:59might want to add additional
  53. 2:00authentication factors to keep anyone
  54. 2:02from connecting to your device from a
  55. 2:04remote location. Attackers love to take
  56. 2:07advantage of open ports for remote
  57. 2:09desktop and easy to find usernames and
  58. 2:11passwords because once they're on a
  59. 2:13system, it's all theirs as if they were
  60. 2:16sitting in front of the computer
  61. 2:17physically. They're able to go through
  62. 2:19all of your files. They're able to
  63. 2:21connect to other sites and they're able
  64. 2:23to perform whatever they'd like to do
  65. 2:25from your machine using remote desktop.
  66. 2:29If you have a mobile device or a laptop
  67. 2:31and you need to connect back to your
  68. 2:33corporate office across the internet,
  69. 2:35then you're probably very familiar with
  70. 2:37a VPN. This is a virtual private network
  71. 2:40and it encrypts all of the data going
  72. 2:42back and forth between you and the other
  73. 2:44device, even if you're going across a
  74. 2:46public network like the internet. From
  75. 2:48your device, you're connecting to a VPN
  76. 2:51concentrator. This is a centralized
  77. 2:53device. Usually, it's at your point of
  78. 2:55business and everyone who needs access
  79. 2:57to your company is going to use the VPN
  80. 2:59client on their computer to connect to
  81. 3:01the VPN concentrator at your corporate
  82. 3:04office. You may find that you have a
  83. 3:06single appliance or server that's
  84. 3:08configured as a VPN concentrator, but
  85. 3:10these days you often find VPN
  86. 3:12concentrators built into next generation
  87. 3:15firewalls. This gives you options as to
  88. 3:17how you'd like to deploy these VPN
  89. 3:19services. You can build your own
  90. 3:20softwarebased VPN or you can use an
  91. 3:23integrated hardwarebased VPN that may be
  92. 3:26part of your nextG firewall. Some VPN
  93. 3:28concentrators require that you install
  94. 3:30special software on your client machine.
  95. 3:33Other operating systems have builtin
  96. 3:35VPNs and you may be able to connect to
  97. 3:37the VPN concentrator using software
  98. 3:39that's already available in Windows,
  99. 3:41Linux, or Mac OS.
  100. 3:44Here's how a VPN works visually. You're
  101. 3:46the remote user at home that needs to
  102. 3:49access resources that are on your
  103. 3:51corporate network, but your only
  104. 3:52connection is through the internet, and
  105. 3:54you certainly don't want to send
  106. 3:55unencrypted information across that
  107. 3:57public network. So, you'll use VPN
  108. 4:00software on your remote device to
  109. 4:02encrypt all of the data sent across the
  110. 4:04internet. And on the other side, the
  111. 4:06device that is acting as your VPN
  112. 4:07concentrator will decrypt that
  113. 4:09information and send it into your
  114. 4:11corporate network. For this information
  115. 4:13to get back to you, we simply reverse
  116. 4:15this process. So information is sent
  117. 4:17from your corporate network. It hits the
  118. 4:19VPN concentrator where it is encrypted,
  119. 4:21sent across the internet, and it's
  120. 4:23decrypted on your local device at home.
  121. 4:26We rely on VPNs to encrypt and secure
  122. 4:28all of the data that we're sending
  123. 4:30across the network. This means that if
  124. 4:32someone's taking a packet capture or has
  125. 4:34some way to view the information that
  126. 4:36we're sending across the network would
  127. 4:37not be able to see any of the data since
  128. 4:40it's all encrypted over the network.
  129. 4:42When you're connecting to that
  130. 4:43concentrator, you're often asked for
  131. 4:45some type of authentication credentials.
  132. 4:48If you're only using a username and
  133. 4:49password, there is a potential that
  134. 4:51someone could perform a brute force
  135. 4:53attack to try to determine the best
  136. 4:55combination to gain access to that
  137. 4:57system. This means that we often have
  138. 4:59additional multiffactor authentication
  139. 5:01that we use during this login process.
  140. 5:04So we might provide a username, a
  141. 5:06password, and then an additional code
  142. 5:08that's provided to us from an app. This
  143. 5:10ensures that only people authorized are
  144. 5:12able to gain access to this virtual
  145. 5:14private network.
  146. 5:17As an administrator, there may be times
  147. 5:19when you need to connect to a remote
  148. 5:21device and be able to make a
  149. 5:22configuration change at the console of
  150. 5:25that device. In order to have a
  151. 5:27protected communication between your
  152. 5:29device and the remote device, you would
  153. 5:31probably use SSH or secure shell. Secure
  154. 5:35shell is designed for terminal
  155. 5:36communication like the one you see here,
  156. 5:38and it uses TCP port 22 in order to
  157. 5:42communicate. This looks and feels very
  158. 5:44similar to the older Tnet protocol which
  159. 5:46runs on TCP port 23, but all of the
  160. 5:49communication used by Tnet is sent in
  161. 5:52the clear across the network. If you
  162. 5:54want to have an encrypted connection to
  163. 5:56that remote device, you'll always want
  164. 5:58to use secure shell.
  165. 6:01There's a great deal of security built
  166. 6:03into SSH, which is why it's a great
  167. 6:05utility to use for connecting to that
  168. 6:07remote terminal. Since all of the SSH
  169. 6:10communication is sent and encrypted,
  170. 6:12there's no way for anyone to perform a
  171. 6:14packet capture and somehow determine
  172. 6:16what your username and password might
  173. 6:18be. You can enhance the use of SSH by
  174. 6:21adding additional authentication
  175. 6:22options. For example, SSH supports the
  176. 6:25use of public private key pairs to add
  177. 6:27additional authentication for connecting
  178. 6:29to that remote device. And as a best
  179. 6:32practice, it's probably a good idea to
  180. 6:34disable any type of remote access to
  181. 6:36certain usernames. For example, the root
  182. 6:39account on a Linux machine is the super
  183. 6:41user of that device, and you probably
  184. 6:44don't want people being able to log in
  185. 6:46as root by using SSH. Some organizations
  186. 6:49have completely removed all
  187. 6:51password-based authentication, and they
  188. 6:53require a certificate to be able to
  189. 6:55authenticate to these remote devices.
  190. 6:58You can enhance this by limiting who's
  191. 7:00able to connect to these remote devices
  192. 7:02based on an IP address. So, you might
  193. 7:04want to configure a filter or network
  194. 7:06firewall to be able to only allow access
  195. 7:10to or from certain IP address ranges.
  196. 7:14Many organizations have outsourced the
  197. 7:16monitoring and ongoing maintenance of
  198. 7:18their networks by using a managed
  199. 7:21service provider or MSP. The MSP will
  200. 7:24often use a tool known as an RMM in
  201. 7:27order to provide that monitoring. RMM
  202. 7:30stands for remote monitoring and
  203. 7:32management. And this provides a way for
  204. 7:34the MSP to be able to monitor and manage
  205. 7:37all of their customers from one single
  206. 7:39console. From this single console, your
  207. 7:42MSP can patch operating systems, log in
  208. 7:45remotely to a device, monitor for any
  209. 7:47security anomalies, and provide
  210. 7:49additional inventory of your hardware
  211. 7:52and software.
  212. 7:53Here's an example of an RMM that I've
  213. 7:56used. You can see on the left side that
  214. 7:58this MSP has six different companies
  215. 8:00that they can access. And right now
  216. 8:02we're looking at company 5 which has
  217. 8:03three different locations in HQ5, LA
  218. 8:06Office 5, and New York Office 5. You can
  219. 8:10see across those we're looking at the LA
  220. 8:12office right now. And the LA office has
  221. 8:14a file server, there's Karen's laptop,
  222. 8:16there's domain controllers and a file
  223. 8:18server. We can also see a status of how
  224. 8:20those devices are running. And we can
  225. 8:22get detailed information about the
  226. 8:24monitoring and ongoing performance of
  227. 8:27each individual device.
  228. 8:30This remote monitoring and management
  229. 8:32tool has access to many different
  230. 8:34customers from one single screen. This
  231. 8:36makes it very attractive to an attacker
  232. 8:38because once they get access to the RMM,
  233. 8:41they now have access to many different
  234. 8:43companies. This is why access to this
  235. 8:45console should be very tightly
  236. 8:47controlled and limited to only the
  237. 8:49authorized users. We might also want to
  238. 8:52require multiffactor authentication to
  239. 8:54anyone who logs into the RMM console.
  240. 8:57and we might want to perform ongoing
  241. 8:59auditing to make sure that we know
  242. 9:01exactly who's connecting to our RMM
  243. 9:03console.
  244. 9:06As our cloud infrastructures became
  245. 9:08larger and larger, we needed a better
  246. 9:10way to remotely connect and manage these
  247. 9:12virtual machines. We were able to
  248. 9:14provide that by using Spice. This is the
  249. 9:17simple protocol for independent
  250. 9:19computing environments. This allows us
  251. 9:21to view and control the remote desktop
  252. 9:24on a virtual machine using a very
  253. 9:26lightweight and easy to use protocol.
  254. 9:29This provides a seamless remote control
  255. 9:31solution across many different operating
  256. 9:34systems running in many different
  257. 9:36virtual machines. If you've ever used
  258. 9:38any type of remote control software,
  259. 9:40then running a Spice protocol
  260. 9:42application is going to be very similar.
  261. 9:44Spice excels by having very efficient
  262. 9:47graphics rendering and very fast
  263. 9:49response times. and you're able to
  264. 9:50integrate with that remote operating
  265. 9:52system by sharing the folder and
  266. 9:54clipboard between your device and the
  267. 9:56spice enabled virtual machine.
  268. 10:00When you run a script in Windows, you
  269. 10:02have to connect to that Windows machine,
  270. 10:04run the script, and then be able to see
  271. 10:06the results of that script on something
  272. 10:08like a remote desktop or remote terminal
  273. 10:11screen. But what if you could send that
  274. 10:13script to a third-party Windows device,
  275. 10:16have it run the script, and then have
  276. 10:18all the results of that script sent back
  277. 10:19to you without directly connecting to
  278. 10:22that remote device. You're able to do
  279. 10:24that by using Windows Remote Management
  280. 10:26or WinRM.
  281. 10:28WinRM is turned on by default on most
  282. 10:31Windows servers. So, all the
  283. 10:32administrator needs to do is send the
  284. 10:34script to that Windows server.
  285. 10:36Obviously, the administrator will need
  286. 10:38to authenticate to that remote device
  287. 10:40when they're sending the script to
  288. 10:42verify that the script is trusted. The
  289. 10:44script then runs on that remote server,
  290. 10:46and the resulting information is all
  291. 10:48sent back to the original screen to be
  292. 10:51able to evaluate what occurred during
  293. 10:53that script.
  294. 10:55I used Winrm on my local device to run a
  295. 10:58script on an external server. My local
  296. 11:01device is the NACO lab server and I'm
  297. 11:04connecting to a server that's elsewhere
  298. 11:05on the network called Atlantis Lab PC.
  299. 11:08I'm running a script that performs a get
  300. 11:10wmi object of all the Win32 services.
  301. 11:13So, this should tell me all the services
  302. 11:15running on that remote device. When I
  303. 11:18send this information over, it asks for
  304. 11:20authentication. I add my username and my
  305. 11:22password. And what I receive in return
  306. 11:24are the results of that script that have
  307. 11:26run on that remote server. I didn't have
  308. 11:29to perform a remote desktop to that
  309. 11:31device or interactively connect through
  310. 11:33a console or terminal. I simply used
  311. 11:35WinRM to run that script remotely.
  312. 11:40You might also find a number of
  313. 11:41thirdparty tools that provide a number
  314. 11:43of different remote management
  315. 11:44capabilities. For example, if you need
  316. 11:46to perform screen sharing, you can use
  317. 11:48Go to My PC, Team Viewer, or similar
  318. 11:51third-party utility. If you want to be
  319. 11:53able to video conference, there are many
  320. 11:55options available on the market. Two of
  321. 11:57the most popular are Zoom and Webex. You
  322. 12:00might also find tools that allow you to
  323. 12:02easily store and transfer files between
  324. 12:05systems. If you're using Dropbox,
  325. 12:07Box.com, or Google Drive, then you've
  326. 12:09taken advantage of some of this file
  327. 12:11synchronization technology. Or if you're
  328. 12:14performing ongoing desktop management of
  329. 12:16a system where you're monitoring and
  330. 12:18updating those systems, you might be
  331. 12:20using Citrix Endpoint Management or
  332. 12:22Manage Engine Desktop Central. All of
  333. 12:25these thirdparty utilities have
  334. 12:26advantages and disadvantages, but the
  335. 12:29key to all of them is making sure that
  336. 12:30we use appropriate security,
  337. 12:32multiffactor authentication, and limit
  338. 12:35access to only the people who are
  339. 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.