7.1. Detailed procedures for generating and installing TLS certificates on ASGARD and Master ASGARD¶
There are several methods to sign the ASGARD generated CSR request. This section describes the two most common procedures.
7.1.1. Use Case 1 - CSR Signing with a Microsoft Based CA¶
Open the Certificate Authority snap-in within Windows Server
Right click your CA >> All Tasks >> Submit new request
Locate and open the signing request file we’ve saved in previous steps
Navigate to the “Pending Requests” within your CA snap-in and right click the imported CSR >> All Tasks >> Issue
Once the certificate has been issued, it will be located under “Issued Certificates”
Right click on the issued certificate and click open
Inspect the information of the Certificate and continue to the next step, if the presented data is correct.
Check that the generated certificate has a status of OK
Navigate to the Details tab and click “Copy to File…”
On the Certificate Export Wizard – click Next
Select Base-64 encoded X.509(.CER) and click Next
Choose an output location and click Next
Click Finish - Once the confirmation message box pops up, click OK
Navigate to Settings >> TLS.
On the bottom of the page click “Upload TLS Certificate” and select the exported certificate from the previous step.
If all steps were followed, a message box should pop up indicating that the certificate was successfully installed.
Navigate to Settings >> Services and restart the “ASGARD 2 Service” by clicking the icon.
Please take into consideration that it could take a few minutes until the ASGARD Service is restarted successfully.
After the service has been successfully restarted, the installed certificate is shown in the browser.
7.1.2. Use Case 2 - CSR Signing with an OpenSSL Based CA¶
In order to avoid security warnings* on some browsers, the CA signing process needs to ensure to copy all Subject Alternative Name (SAN) from the CSR to the signed Certificate.
One way of including all extensions from the CSR to the new certificate, is via the openssl.cnf file, by setting the copy_extensions attribute to copy.
[ CA_default ]
copy_extensions = copy
- These security warnings are result of an incomplete signing process where requested attributes from the CSR are not included in the signed certificates
Prepare the CA certificate, CA private key and the certificate signing request
Execute/adapt following command:
openssl ca -cert cacert.pem -keyfile cakey.pem -in asgard-test01.csr -out asgard-test01.crt -days 3650
Enter the passphrase for your CA’s private key
Confirm that the data contained in the CSR is accurate and confirm the signing of the request to the CA.
Once confirmed commit the changes to your local DB.
As a result, the signed certificate will be available with the indicated filename.
As a last step, the generated certificate can be imported following the Certificate Import steps.
7.2. Migrating agents from ASGARD V1 to ASGARD V2¶
This document will guide customers with an existing ASGARD version 1.x installation to perform an agent migration from ASGARD version 1.x to ASGARD version 2.
The new release of ASGARD Management Center brings not only a totally redesigned interface, but also major changes in the architecture and usability, making it faster, more robust and easier to use.
You need to prepare some data prior to starting the migration.
220.127.116.11. Account Data and Network Access¶
Ensure you have access and credentials to the following systems, as well as connectivity as follows:
- ASGARD Management Center version 1
- Administrative Web User
- Credentials for the ssh user: bsk
- ASGARD Management Center version 2
- Administrative Web User
- Credentials for the ssh user: nextron
- Connectivity between ASGARD 1 and ASGARD 2
- Required only if new agents are transferred via SCP
- Client/Server System(s) connected to ASGARD v1 needs connectivity to ASGARD v2
- Access to a new update server
Identify the systems you want to migrate and perform the following actions on each of the same.
18.104.22.168. Identify the system to be migrated¶
Connect to your ASGARD Management Center version 1.x and identify the system you plan to migrate.
22.214.171.124. Transfer the new ASGARD Windows agent to the ASGARD version 1.x Server¶
Connect to your new ASGARD version 2 server over SSH and transfer the new windows agent to the old ASGARD version 1 server.
This step will allow the old ASGARD version 1.x server to distribute the new agent.
Information: In this step you require the password of your ASGARD version 1.x and your ASGARD version 2.x
126.96.36.199.1. Connect to ASGARD version 2 over SSH¶
188.8.131.52.2. Copy the new agent(s) to ASGARD version 1.x¶
You will find all new agents under
/var/lib/nextron/asgard2/installer, this example will cover a migration of a windows x64 system. Please refer to section 184.108.40.206.8 and 220.127.116.11.9 for Linux/macOS hosts.
sudo scp /var/lib/nextron/asgard2/installer/asgard2-agent-windows-amd64.exe ``firstname.lastname@example.org:/home/bsk` <mailto:email@example.com:/home/bsk>`_
18.104.22.168.3. Check that the new agent has been transferred to the old ASGARD version 1.x Server¶
22.214.171.124.4. Sign the new agents in order to be able to distribute them via GRR¶
sudo grr_config_updater upload_exe --file **asgard2-agent-windows-amd64.exe** --dest_path
**windows** --arch **amd64**
Please modify any variable data from the above command.
Remember to save the “–dest_path”. In our case it is aff4:/asgardv1.nextron/asgard2-agent-windows-amd64.exe
126.96.36.199.5. Switch to Advanced Mode within GRR¶
Open your ASGARD version 1.x web interface and navigate to the Response Control. You will be prompted for a username and password, use the same login information as you use to log into ASGARD.
Once you reach the Response Control Section (GRR) please navigate to the top right corner (settings gear) and switch to the Advanced Mode. Apply the settings.
188.8.131.52.6. Asset Selection¶
Navigate to the
Asset List section on the left menu and select the asset you want to migrate. A click on the asset will select it.
Once the asset has been selected (clicking on it), navigate to the
Start new flows section, located on the left menu.
184.108.40.206.7. Install the new ASGARD2 Agent¶
In order to install the new agent, we will need to expand the
Administrative folder and select
We will be requested to put in a binary, please use the binary name we gathered/created in step 220.127.116.11.4. and click Launch.
The used binary name was extracted from step 18.104.22.168.4. In this example
After approximately 10 minutes, the binary will be executed and installed on the selected system. The status can be retrieved by navigating to the
Manage launched flows section on the left menu.
22.214.171.124.8. Linux Hosts¶
For migrating Linux hosts please create a shell script and follow the above procedure to deploy it.
An example shell script for Debian based systems could look like this:
wget -O agent-linux.deb --no-check-certificate https://asgardv2:8443/agent-installers?asgard2-agent-linux-amd64.deb
dpkg -i /tmp/agent-linux.deb
rm -f /tmp/agent-linux.deb
Save this script in your ASGARDv1 and sign/upload it to GRR as described in point 126.96.36.199.4, afterwards you will be able to launch a HUNT to your connected Linux Systems.
Please bear in mind that the above script will work only for Ubuntu/Debian systems and needs to be adapted for
188.8.131.52.9. macOS Hosts¶
For migrating macOS hosts please create a shell script and follow the above procedure to deploy it.
An example shell script for macOS based systems could look like this:
curl -o agent-darwin.pkg -k "https://asgardv2.bsk:8443/agent-installers?asgard2-agent-macos-amd64.pkg"
sudo installer -pkg /tmp/agent-darwin.pkg -target /
rm -f /tmp/agent-darwin.pkg
Save this script in your ASGARDv1 and sign/upload it to GRR as described in point 184.108.40.206.4, afterwards you will be able to launch a HUNT to your connected
7.2.3. Migration check and completion¶
After the above steps have been executed, the agent should be reporting to the new ASGARD version 2.x server.
At this moment the system will have 2 agents installed, the agent reporting to ASGARD version 1.x and the agent reporting to ASGARD version 2.x
220.127.116.11. Accept the agent request¶
Once a new agent is reporting to ASGARD version 2.x it will automatically create a request to be part of the same. We need to accept that request.
Log into ASGARD version 2.x and navigate to the Asset Management – Requests.
Select the migrated system and click on the top right on Accept. This should place the system in the
7.2.4. Frequently Asked Questions¶
This section will cover frequent questions regarding the migration.
18.104.22.168. Will there be any problem in running both agents at the same time?¶
There are no known issues running both agents at the same time. The new ASGARD v2 agent is more lightweight and performant. The expected RAM utilization in idle mode demonstrated in our tests put the new agent in a very good position, consuming only 1 MB.
22.214.171.124. Will I need more resources for my new ASGARD v2 server?¶
Please refer to the ASGARD v2 manual for specific sizing. The overall tests performed highlight that both server and agents are more performant which will allow more agent management per ASGARD (compared to version 1).
126.96.36.199. Can I import my memory dumps and file collections made on ASGARD v1?¶
Unfortunately importing memory dumps and/or file collections made on ASGARD v1 is not possible.