Parcourir la source

Phantom & Tenable Notes

Brad Poulton il y a 4 ans
Parent
commit
a6d2d8c5bc
2 fichiers modifiés avec 45 ajouts et 23 suppressions
  1. 25 23
      Phantom Upgrade Notes.md
  2. 20 0
      Tenable Notes.md

+ 25 - 23
Phantom Upgrade Notes.md

@@ -16,28 +16,6 @@ TODO: Switch to a non-root installation! Future Upgrade may force us to switch.
 # Upgrade Steps
 See Splunk docs!
 
-## Take a backup
-
-> :warning: Silence Phantom Sensu checks
-
-Stop Phantom 
-`/opt/phantom/bin/stop_phantom.sh`
-
-Take an AWS snapshot OF ALL DRIVES in addition to the automatic snapshots! Phantom uses the /tmp directory in addition to the /opt directory. Be sure to include the EBS volume that is storing the /opt data. It is 500 GB volume ( prod ) or a 60 GB volume ( TEST ).
-```
-Naming Scheme: phantom-pre-upgrade-backup-<current-version>
-phantom-pre-upgrade-backup-4.10.6
-```
-
-Take a full phantom backup while phantom is running. NOTE: to restore a phantom backup you must restore it to the same version of Phantom on a different server! You CAN skip the ibackup if you have a good snapshot!  
-`/opt/phantom/bin/start_phantom.sh`  
-`/opt/phantom/bin/phenv ibackup --setup`  
-`/opt/phantom/bin/phenv ibackup --backup`  
-
-## Prerequisites
-Be sure you have enough space!
-`df -h | grep opt`
-
 ## Prep 
 
 Calendar Invite for PROD Phantom Upgrade. Coordinate with James Kerr and Greg Rivas for a time that works with the SOC.
@@ -69,6 +47,28 @@ Post to xdr-soc
 Phantom is shutting down for an update in 5 minutes!
 ```
 
+## Take a backup
+
+> :warning: Silence Phantom Sensu checks
+
+Stop Phantom 
+`/opt/phantom/bin/stop_phantom.sh`
+
+Take an AWS snapshot OF ALL DRIVES in addition to the automatic snapshots! Phantom uses the /tmp directory in addition to the /opt directory. Be sure to include the EBS volume that is storing the /opt data. It is 500 GB volume ( prod ) or a 60 GB volume ( TEST ).
+```
+Naming Scheme: phantom-pre-upgrade-backup-<current-version>
+phantom-pre-upgrade-backup-4.10.4-2
+```
+
+Take a full phantom backup while phantom is running. NOTE: to restore a phantom backup you must restore it to the same version of Phantom on a different server! You CAN skip the ibackup if you have a good snapshot!  
+`/opt/phantom/bin/start_phantom.sh`  
+`/opt/phantom/bin/phenv ibackup --setup`  
+`/opt/phantom/bin/phenv ibackup --backup`  
+
+## Prerequisites
+Be sure you have enough space!
+`df -h | grep opt`
+
 
 1. Stop Phantom  
 `/opt/phantom/bin/stop_phantom.sh`
@@ -84,10 +84,12 @@ grep archive_mode /opt/phantom/data/db/postgresql.phantom.conf
 
 4. install updates excluding nginx.
 
-> :warning: Watch out for the phantom_repo package being updated! Do not update phantom_repo, yet. If phantom is not running i don't think the package upgrade succeeds. Reboot if kernal is updated.
+> :warning: Watch out for the phantom_repo package being updated! Do not update phantom_repo, yet. If phantom is not running i don't think the package upgrade succeeds. Reboot if kernal is updated or just reboot for funzies.
 `yum update --exclude=nginx --disablerepo phantom-base`
 `shutdown -r now`
 
+`ping phantom-0` 
+
 5. Start Phantom ( should be already started due to reboot )
 `/opt/phantom/bin/start_phantom.sh`
 

+ 20 - 0
Tenable Notes.md

@@ -3,11 +3,30 @@
 
 ## Service
 `systemctl status SecurityCenter`
+`systemctl start nessusd`
+`systemctl status nessusagent`
+
+Show Version
+`sudo /opt/nessus/sbin/nessuscli -v`
+`sudo /opt/nessus_agent/sbin/nessuscli -v`
 
 ## Log location
 /opt/sc/admin/logs
 /opt/sc/support/logs
 
+## Upgrading
+- Download the latest RPM from https://www.tenable.com/downloads/nessus
+- Check the sha256 on your mac with `shasum -a 256 Nessus-8.15.1-es7.x86_64.rpm`
+- Use teleport to scp the file to the test and prod repo server
+- Update the tenable repo per the Reposerver Notes.md
+- Run `yum clean all && yum update` on the appropriate server to update the software from the repo server
+- For Nessus, you need to start the software after the upgrade with `systemctl start nessusd.service`
+- To ensure everything is working, log into Tenable.sc with admin creds and look at the Resources > Nessus Scanners then click on Options > Update Status
+- If the Scanner shows a status of "Protocol Error" you were too fast and need to be patient; go browse a conservative news source for 5 minutes ;-)
+
+NOTE: The Tenable Agents upgrade themselves through the Nessus Manager. 
+
+
 ## General Setup
 
 ### svc-scan
@@ -21,6 +40,7 @@ See https://community.tenable.com/s/article/Upload-a-Custom-CA-certificate-custo
 These certs include the xdr root ca and intermediate from XDR WWW Certificates Subordinate CA v2 in AWS. I also grabbed the MDR Root CA G1. The Splunk Common CA is the last cert.
 
 custom_CA.inc
+
 ```
 -----BEGIN CERTIFICATE-----
 MIICMDCCAbagAwIBAgIRAMbEtbFaI4iLYDpPJmXv2gEwCgYIKoZIzj0EAwQwWTEL