This message was deleted.
# neuvector-securitya
adamant-kite-43734
02/24/2025, 2:08 PMThis message was deleted.
q
quaint-candle-18606
02/24/2025, 5:49 PMI think the RWO PVC might prove challenging for that, but you could experiment and see?
quaint-candle-18606
02/24/2025, 5:49 PMBest practice is to send security reports to a SIEM for longer-term retention.
f
faint-spring-73056
02/25/2025, 9:10 AMI agree with you about sending the reports to a different system for long term storage but it would be nice to be able to write the configuration to a bucket. We don't have access to RWX PVC volumes so we can't deploy the controller HA
faint-spring-73056
02/25/2025, 9:11 AMWell, we can deploy the controller HA but we don't have a persistent configuration then
q
quaint-candle-18606
02/25/2025, 3:22 PMAs an option, you could manually do backups of the config in the UI, or automate it a bit with the API.
quaint-candle-18606
02/25/2025, 3:23 PMsomething like
Copy code
./config.py export -u admin -w admin -s $_controllerIP_ -p $_controllerPort_ -f $_FILENAME_f
faint-spring-73056
02/25/2025, 3:30 PMThat's actually not a bad idea but how do I get that configuration back into Neuvector when we restart the controller? It seems that, when no PVC is enabled in the Helm chart, the configuration isn't written to disk but lives in memory.
Is it possible to restart Neuvector with that configuration backup so everything is configured correctly?
q
quaint-candle-18606
02/25/2025, 3:42 PMYes! You can restart NeuVector and it will look just like a fresh install (naturally). Then just restore the config in Settings... Configuration. It's pretty quick and easy.
quaint-candle-18606
02/25/2025, 3:42 PMf
faint-spring-73056
02/25/2025, 3:58 PMThanks! This looks like something that could work for us
🦜 1
4 Views