oxbrbtx/PrimAITE
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

#2689 Addressed more PR comments & fixed an bug with command parsing in _command_terminal (c2 beacon)

Browse Source
This commit is contained in:
Archer Bowen
2024-08-16 10:24:53 +01:00
parent e5be392ea8
commit 849cb20f35
6 changed files with 41 additions and 32 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
src/primaite/notebooks/Command-&-Control-E2E-Demonstration.ipynb
View File

@@ -191,7 +191,7 @@
"Before the Red Agent is able to perform any C2 specific actions, the C2 Server needs to be installed and run before the Red Agent can perform any C2 specific action.\n",
"This is because in higher fidelity environments (and the real-world) a C2 server would not be accessible by a private network blue agent and the C2 Server would already be in place before the an adversary (Red Agent) starts.\n",
"\n",
"The cells below install and runs the C2 Server on client_1 directly via the simulation API."
"The cells below install and run the C2 Server on client_1 directly via the simulation API."
]
},
{
@@ -1188,7 +1188,7 @@
"source": [
"#### Shutting down the node infected with a C2 Beacon.\n",
"\n",
"Another way a blue agent can prevent the C2 suite is by shutting down the C2 beacon's host node. Whilst not as effective as the previous option, dependant on the situation (such as multiple malicious applications) or other scenarios it may be more timestep efficient for a blue agent to shut down a node directly."
"Another way a blue agent can prevent the C2 suite is by shutting down the C2 beacon's host node. Whilst not as effective as the previous option, depending on the situation (such as multiple malicious applications) or other scenarios it may be more timestep efficient for a blue agent to shut down a node directly."
]
},
{
@@ -1216,7 +1216,7 @@
"cell_type": "markdown",
"metadata": {},
"source": [
"The code cell below uses the custom blue agent defined at the start of this section perform a ``NODE_SHUT_DOWN`` action on the web server."
"The code cell below uses the custom blue agent defined at the start of this section to perform a ``NODE_SHUT_DOWN`` action on the web server."
]
},
{
@@ -1233,7 +1233,7 @@
"cell_type": "markdown",
"metadata": {},
"source": [
"Which we can see the effects of after another timestep and looking at the web_server's operating state & the OBS differences."
"Which we can see the effects of after another timestep and looking at the web server's operating state & the OBS differences."
]
},
{
@@ -1454,7 +1454,7 @@
"\n",
"In the case of the C2 Beacon, the C2 Server's IP address must be supplied before the C2 beacon will be able to perform any other actions (including ``APPLICATION EXECUTE``).\n",
"\n",
"If the network contains multiple C2 Servers then it's also possible to switch to different C2 servers mid-episode which is demonstrated in the below code cells."
"If the network contains multiple C2 Servers then it's also possible to switch to a different C2 servers mid-episode which is demonstrated in the below code cells."
]
},
{
@@ -1544,7 +1544,7 @@
"cell_type": "markdown",
"metadata": {},
"source": [
"After six timesteps the client_1 server will recognise the C2 beacon's previous connection as dead and clear its connections. (This is dependant on the ``Keep Alive Frequency`` setting.)"
"After six timesteps the client_1 server will recognise the C2 beacon's previous connection as dead and clear its connections. (This is dependent on the ``Keep Alive Frequency`` setting.)"
]
},
{