BUILDING A LINUX FIREWALL
BUILDING NIDS WITH SNORT
NETWORK MONITORING WITH MRTG
NETWORK MONITORING WITH NAGIOS
Duration 6 Hours
Your company can't afford a dedicated leased line for connecting various branch offices. They however, want to grant safe, controlled access to the company’s network for telecommuters, and branch offices via the untrusted Internet. For setting up the controlled network, they need a program that is free of cost, open source, easy to administer, secure, and platform-independent.
An obvious choice will be OpenVPN. But why?
The technology, Virtual Private Networks (VPN) is new to me. What is it about?
Given all communications will be done over untrusted networks, which cryptographic protocols can I use to protect against eavesdropping, message forgery, tampering and also provide authentication?
Why would I consider using one cryptographic protocol over another?
Because VPN is heavily dependent on encryption, I'll need encryption keys or even best, set up my own Public Key Infrastructure (PKI). How can I make this possible?
I will also need a simple OpenVPN test lab. What do I need, and how can I implement one?
My lab is ready to go, how can I set up an OpenVPN Server for multiple clients
I will also need to connect Linux and Windows Clients. Stepwise, how can I accomplish that?
   
Practise Labs
Working with openSSL
Installing OpenVPN from sources
Setting up an OpenVPN test lab
Testing Encryption with static keys
Connecting a Remote Linux client using static keys
Creating your own PKI for OpenVPN
Configuring the OpenVPN server for multiple clients
Setting OpenVPN server in Bridge mode
Revoking certificates
Running OpenVPN as a non-privileged user
Connecting Remote Windows clients