- Hello, and welcome to the Caldera installation video.
Today I'll be taking you through the steps
to setup a Caldera environment
and get you using Caldera today.
We'll begin by cloning the github project
and installing the required dependencies.
When cloning the repository, remember,
you can specify a branch or a release.
Here, we're cloning "master"
to have the latest code contributed to Caldera.
After the cloning is finished,
CD into the Caldera directory
and install the dependencies via the pip3 utility.
Now we're ready to run Caldera.
Run the command on the screen
to launch the Caldera server,
and then browse the logo host, port 8888,
to be greeted with a login prompt.
The credentials are "admin" "admin".
Then you will be greeted with the Caldera splash page.
Please note the banner at the top of the splash page.
Google Chrome is the only supported browser for Caldera.
Before interacting with the remote host,
you must first deploy an agent.
Sandcat is the default agent that ships with Caldera.
In this tutorial, we will show you
how to configure and deploy a Sandcat agent
for your desired operating system.
The image on the screen depicts a typical Sandcat work flow.
First, the operator will use
the operating system specific command
to download and execute Sandcat on the target host.
After Sandcat's been downloaded and executed,
it will call back to the Caldera instance.
Now we're ready to begin operations and task the agent.
After selecting the Sandcat plugin
in the top right corner of the home splash page,
you will be redirected to the Sandcat splash page.
To the left you will see a brief description about Sandcat,
as well as a dropdown menu to select your target OS.
Each menu sub-item contains an operating system
appropriate command that will download Sandcat
from your Caldera instance
and execute Sandcat on the target host.
In this example, we will be running
and executing Sandcat locally.
The default Sandcat one-liners contain verbose output
so you can immediately see whether or not you are successful
and having your agent callback to your Caldera instance.
The agent's tab underneath the campaign's menu item
will show you the current status of the Sandcat agents
that are calling back to your Caldera instance.
The agent's page lets you see meta data pertaining
to the agent that you ran on the target host
as well as control configurable options
such as the sleep time, a group rating,
and whether or not the agent is trusted.
Before we begin our operation,
let's cover some Caldera terminology.
Adversaries contain abilities that are used
to run operations.
Abilities consist of commands that are executed
on the remote host.
Multiple abilities can be strung together
to create an adversary profile.
Let's begin by creating an operation call test
and assigning it the adversary profile of Mission 1.
We will then task it to my group, which is our Sandcat agent
that is currently executing on the target host.
To the left, you will see colored circles
indicating the status of the ability
being executed on the host.
Green meaning success, and red meaning failure.
Double clicking on these abilities will show information
about what's being run on the host itself.
Clicking the star icon will show more information
about what success or failure means in each ability.
Here we see an ability failed
because pip was not on the target machine.
The center white bar shows the percentage
of the operation that's already been completed.
These buttons allow you to pause the operation altogether,
execute the operation with one ability at a time,
or execute the ability sequentially, as we've already seen.