SEC 250
Remote Access
ACCESSING HOSTS & DATA
The most common method you’ve used in your tech experience has been accessing hosts & data locally
What does that look like?
You on keyboard using credentials in same OS
ACCESSING STUFF … REMOTELY?
As you progress in more complex environments, another common method is accessing hosts & data remotely
Or in other words: accessing logon credentials which are created, managed & stored on another host’s OS, different than the one you physically are on now.
You on keyboard here
Credentials in this OS
REMOTE ACCESS
We will explore two common protocols which allow remote access:
SSH: SECURE SHELL
Protocol using asymmetric encryption (hence the “secure”) for authentication & communication
Default port: TCP 22
Used mostly for terminal command line interfaces (CLIs)
THE “go to” for secure channels in Linux
Remind me: How does this type of crypto work?
RDP: REMOTE DESKTOP PROTOCOL
Protocol (proprietary by Microsoft) using symmetric streaming encryption (RC4)
Default ports: TCP & UDP 3389
Wrapped into more software (Remote Desktop Connection, Terminal Services, or whatever Microsoft rebrands it)
Aim: to provide entire Desktop experience, remotely
Remind me: How does this type of crypto work?
C-I-A SPOT CHECK
How does remote access deal with C-I-A?
They are extremely helpful, and it’s great these protocols provide “secure” communications …
However, they also provide: