anchor.diff:  
   == Overview
   
  -Working in pairs or 3s, you will run an "inside-out" vulnerability scan on and a simple "outside-in" scan on the servers. (By splitting up, more of you can be more hands-on.) The testing will be performed by downloading two vulnerability scanners and running them on your servers.
  +Working in pairs or 3s, you will run an "inside-out" vulnerability scan and a simple "outside-in" scan on the servers. (By splitting up, more students can be hands-on with the lab.) The testing will be performed by downloading two vulnerability scanners and running them on your servers.
   
   You will research the results and recommend at least one fix that can be implemented in the Vagrantfile and associated cookbook and/or shell script for building the server.
   
  
positive.code: 
  OpenSCAP will return a large number of vulnerabilities. Some of them can be easily remediated. Others would be more difficult. You can easily research them using Google.
  
  Scroll through the output. Note the following:
  
  ....
  Title   Specify a Remote NTP Server
  Rule    xccdf_org.ssgproject.content_rule_ntpd_specify_remote_server
  Ident   CCE-27098-3
  Result  fail
  ....
  
  What is NTP and why is its absence a problem? Research as a team. We will discuss in class.
  
negative.code: === Getting started
  Your public1-4 pipelines are still operational. Refer back to previous labs (`su publicxx, cd ~/Calavera`).
  
  We are going to focus on caraxx and espinaxx since hackers would likely try to exploit these servers first. Why? Because these two environments contain production code. This gives your team 2 servers to work with.
  
  Restart the virtual servers by doing "vagrant up" on:
  
  * espinaxx
  * caraxx
  