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

#2837 - Actioning review comments and fixing a bug with links to the common attributes within software documents

Browse Source
This commit is contained in:
Charlie Crane
2024-09-05 11:23:52 +01:00
parent 3feb908900
commit fcbde31dad
16 changed files with 24 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/source/simulation_components/system/applications/c2_suite.rst
View File

@@ -59,7 +59,7 @@ Once installed and configured; the C2 beacon can establish connection with the C
This will send an initial ``keep alive`` to the given C2 Server (The C2 Server IPv4Address must be given upon C2 Beacon configuration).
Which is then resolved and responded by another ``Keep Alive`` by the C2 server back to the C2 beacon to confirm connection.
The C2 Beacon will send out periodic keep alive based on it's configuration parameters to configure it's active connection with the C2 server.
The C2 Beacon will send out periodic keep alive based on its configuration parameters to configure it's active connection with the C2 server.
It's recommended that a C2 Beacon is installed and configured mid episode by a Red Agent for a more cyber realistic simulation.
@@ -254,12 +254,6 @@ Via Configuration
C2 Beacon Configuration
=======================
``Common Attributes``
"""""""""""""""""""""
See :ref:`Common Configuration`
``c2_server_ip_address``
""""""""""""""""""""""""
@@ -308,12 +302,18 @@ This must be a string i.e ``DNS``. Defaults to ``HTTP``.
*Please refer to the ``IPProtocol`` class for further reference.*
``Common Attributes``
^^^^^^^^^^^^^^^^^^^^^
See :ref:`Common Configuration`
C2 Server Configuration
=======================
*The C2 Server does not currently offer any unique configuration options and will configure itself to match the C2 beacon's network behaviour.*
``Common Attributes``
"""""""""""""""""""""
^^^^^^^^^^^^^^^^^^^^^
See :ref:`Common Configuration`

2
docs/source/simulation_components/system/applications/data_manipulation_bot.rst
View File

@@ -201,6 +201,6 @@ The chance of the ``DataManipulationBot`` to succeed with a data manipulation at
This must be a float value between ``0`` and ``1``.
``Common Attributes``
"""""""""""""""""""""
^^^^^^^^^^^^^^^^^^^^^
See :ref:`Common Configuration`

2
docs/source/simulation_components/system/applications/database_client.rst
View File

@@ -106,6 +106,6 @@ Optional. Default value is ``None``.
The password that the ``DatabaseClient`` will use to access the :ref:`DatabaseService`.
``Common Attributes``
"""""""""""""""""""""
^^^^^^^^^^^^^^^^^^^^^
See :ref:`Common Configuration`

2
docs/source/simulation_components/system/applications/dos_bot.rst
View File

@@ -158,6 +158,6 @@ The maximum number of sessions the ``DoSBot`` is able to make.
This must be an integer value equal to or greater than ``0``.
``Common Attributes``
"""""""""""""""""""""
^^^^^^^^^^^^^^^^^^^^^
See :ref:`Common Configuration`

2
docs/source/simulation_components/system/applications/ransomware_script.rst
View File

@@ -81,6 +81,6 @@ IP address of the :ref:`DatabaseService` which the ``RansomwareScript`` will enc
This must be a valid octet i.e. in the range of ``0.0.0.0`` and ``255.255.255.255``.
``Common Attributes``
"""""""""""""""""""""
^^^^^^^^^^^^^^^^^^^^^
See :ref:`Common Configuration`

2
docs/source/simulation_components/system/applications/web_browser.rst
View File

@@ -108,6 +108,6 @@ The domain ``arcd.com`` can be matched by
``Common Attributes``
"""""""""""""""""""""
^^^^^^^^^^^^^^^^^^^^^
See :ref:`Common Configuration`