# Securing localhost-only machine **URL:** \ **Category:** Configuration\ **Created:** [December 21, 2019, 2:42am UTC](https://discuss.aerospike.com/t/securing-localhost-only-machine/6973 "2019-12-21T02:42:53Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Kiswono\_Prayogo](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/kiswono_prayogo/32/667_2.png) [@Kiswono\_Prayogo](https://discuss.aerospike.com/u/Kiswono_Prayogo)\ **Post date:** [December 21, 2019, 2:42am UTC](https://discuss.aerospike.com/t/securing-localhost-only-machine/6973/1 "2019-12-21T02:42:53Z")
Is it safe only doing this? ```auto sudo sed -i "s/address any/address 127.0.0.1/g" /etc/aerospike/aerospike.conf cat /etc/aerospike/aerospike.conf | grep address sudo systemctl restart aerospike ``` or other ports (3001,3003) also need to be secured to localhost (if it so, how?) ```auto $ sudo netstat -antp | grep as tcp 0 0 127.0.0.1:3000 0.0.0.0:* LISTEN 17855/asd tcp 0 0 0.0.0.0:3001 0.0.0.0:* LISTEN 17855/asd tcp 0 0 0.0.0.0:3003 0.0.0.0:* LISTEN 17855/asd ``` ---
**Author:** ![kporter](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/kporter/32/515_2.png) [@kporter](https://discuss.aerospike.com/u/kporter)\ **Post date:** [December 26, 2019, 6:43pm UTC](https://discuss.aerospike.com/t/securing-localhost-only-machine/6973/2 "2019-12-26T18:43:48Z")
You also need to configure the `address` configuration for `network.fabric` and `network.info` configuration contexts… ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/system/32/2274_2.png) [@system](https://discuss.aerospike.com/u/system)\ **Post date:** [January 1, 2020, 6:43pm UTC](https://discuss.aerospike.com/t/securing-localhost-only-machine/6973/3 "2020-01-01T18:43:57Z")
This topic was automatically closed 6 days after the last reply. New replies are no longer allowed.