Splunk SOAR (f.k.a. Phantom)

Phantom: Can I disable port 80 on phantom server?

sdubey_splunk
Splunk Employee
Splunk Employee

Phantom: Can I disable port 80 on phantom server?

Is it possible to disable port 80 on Phantom server and what is the impact? We have an internal audit team requesting for port 80 to be closed.

Labels (2)
Tags (1)
0 Karma
1 Solution

sdubey_splunk
Splunk Employee
Splunk Employee
  1. Internal communication happens on 443. We force everything over to 443 as per engineering. (initially I wasn't aware
    that internal communication betwen nginx->wsgi and nginx->postgress happens via 443 ).

  2. I tested in lab :

[root@phantom ~]# netstat -plnt | grep nginx
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3442/nginx: master
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 3442/nginx: master

As per /etc/nginx/conf.d/default.conf:

server {
listen 80 default_server;
server_name _;
charset utf-8;

return https://$http_host$request_uri;
}

Take a backup of /etc/nginx/conf.d/default.conf and vi /etc/nginx/conf.d/default.conf and comment the below lines:

server {

listen 80 default_server;

server_name _;

charset utf-8;

return https://$http_host$request_uri;

}

service nginx restart

Post restart as you can see port 80 is not listening.

[root@phantom ~]# netstat -plnt | grep nginx
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 3549/nginx: master

So it would be safe for them to disable it in the /etc/nginx/conf.d/default.conf only with the caveat of: "If you have anything pointing at http://<phantom_ip/fqdn>/ it is going to break.

View solution in original post

0 Karma

sdubey_splunk
Splunk Employee
Splunk Employee
  1. Internal communication happens on 443. We force everything over to 443 as per engineering. (initially I wasn't aware
    that internal communication betwen nginx->wsgi and nginx->postgress happens via 443 ).

  2. I tested in lab :

[root@phantom ~]# netstat -plnt | grep nginx
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 3442/nginx: master
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 3442/nginx: master

As per /etc/nginx/conf.d/default.conf:

server {
listen 80 default_server;
server_name _;
charset utf-8;

return https://$http_host$request_uri;
}

Take a backup of /etc/nginx/conf.d/default.conf and vi /etc/nginx/conf.d/default.conf and comment the below lines:

server {

listen 80 default_server;

server_name _;

charset utf-8;

return https://$http_host$request_uri;

}

service nginx restart

Post restart as you can see port 80 is not listening.

[root@phantom ~]# netstat -plnt | grep nginx
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 3549/nginx: master

So it would be safe for them to disable it in the /etc/nginx/conf.d/default.conf only with the caveat of: "If you have anything pointing at http://<phantom_ip/fqdn>/ it is going to break.

0 Karma
Get Updates on the Splunk Community!

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...

.conf24 | Learning Tracks for Security, Observability, Platform, and Developers!

.conf24 is taking place at The Venetian in Las Vegas from June 11 - 14. Continue reading to learn about the ...

Announcing Scheduled Export GA for Dashboard Studio

We're excited to announce the general availability of Scheduled Export for Dashboard Studio. Starting in ...