anchor.diff:  === 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, as these would likely be the servers first exploited by hackers. This gives your team 2 servers to work with.
  -
  -Restart them by doing "vagrant up" on:
  +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
  
positive.code: 
  == 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.
  
  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.
  
  
negative.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.
  
  The `run_test.sh` script creates an HTML vulnerability scan report in the current working directory called `results.html`. An easy way to view this report is to install a text-based web browser:
  
    sudo apt-get install lynx-cur
  
  Then, you can view the report in your terminal window by running the command:
  
    lynx results.html
  
  Scroll through the report. Click on the following link:
  
  ....
  Specify a Remote NTP Server          fail
  ....
  
  What is NTP and why is its absence a problem? Research as a team. We will discuss in class.
  