Hi there guys, we are a company that develops software for a small company. We have developed an app that makes a connection to a box server in the company using Domino Access services. It is a REST API https connection. The app is making a GET request and server sends back data in JSON format. Our app is hosted in IBM Cloud and it has public url it uses for communication. The IT security of the company is managed by a different IT technical support company and they are using FortiGate 90e firewall. The person configuring this firewall was unable to quickly have a suitable solution on how to restrict EVERYTHING else from communicating with server except that one app that has dedicated URL. We tried to block connection based on IP, but since the app is hosted in the cloud IPs can change, we were given IP ranges by IBM, but they don't even match the IP of request of the app. So we are thinking on restricting everything except these https requests from an app that was given URL by IBM cloud in the form of: "myFancyApp.mybluemix.net." Can anyone please kindly guide us through making that nice helpful person through configuring his Fortigate 90e firewall to allow our app to communicate through firewall with that server and block everything else in the world ? We will appreciate any links to "cookbooks" and advice, thank you most kindly in advance.
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hi,
You can make it possible with static URL filter option in FortiGate.
1. First Line: First Simply allow the Simple URL (Your static URL)
2. Second Line: Block "mybluemix.net" with the wildcard.
Hi
WIth the IPv4 policy it still should be possible, given that either a) you know the IP address or range the http get request comes from or b) you can limit the origin of the http get request to an FQDN (or a number of them) and do not need to use a wildcard FQDN. This way you don't need to use a web filter at all. The policy would look something like the attached picture (you still can add multiple FQDNs to the source but not a wildcard FQDN).
By the way, I am just thinking, maybe it would be possible with the application control feature, but I'm not enough into it to tell you that exactly.
See if that works for you!
You should use some type auth at the app like a API-KEy but that's not for me to debate. Is the RESTful call done thru HTTP or HTTPS?
PCNSE
NSE
StrongSwan
Thanks for responding. It is IBM Domino Server, it is secured by SHA2 and it has encryption certificate, http connections are not allowed. The app is making htttps GET requests, the server returns data in JSON format. With firewall on, connections from app hosted in the IBM cloud are timing out and failing, when firewall was disabled for 5 minutes, we could get connection back from server. The server is dedicated to provide data to that one single app and nothing else. We are trying to figure out how to explain firewall administrator how to configure his managed firewall.
Not to rain on your parade, but that sounds more like a web server configuration to me.
Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com
If: 1. He had firewall on and app couldn't connect. And: 2. He had turned it off for 5 minutes and we could connect. Then it is firewall issue or do you mean it is "web server configuration" option somewhere in the options of the firewall ? Before that we tried IP restriction, but because it is a cloud app, we don't have a guaranteed static IP address, it keeps changing.
We were thinking maybe he has to create whitelist web filter and add a record looking like: *.mybluemix.net or maybe the full URL of the app like: "myFancyApp.mybluemix.net" Or is the whitelist web filter only for outgoing http requests ? Does anyone have any clue or scripting links/examples on how to make the URI resources hosted by that server accessible only to the app that has URL: "myFancyApp.mybluemix.net" ? To rephrase the explanation here - it is webserver hosting data and displaying it in JSON format as REST api. We need this server locked down and blocked from any incoming connections except one app located at "myFancyApp.mybluemix.net" making https GET requests to retrieve data in JSON format on that server on various URIs with the help of Fortigate 90e firewall through which all of this communication is happening.
Hi,
You can make it possible with static URL filter option in FortiGate.
1. First Line: First Simply allow the Simple URL (Your static URL)
2. Second Line: Block "mybluemix.net" with the wildcard.
Good sir, I thank you most kindly ! I don't know yet if I can make use of this, and if it works, but it most definitely answers the question I asked.
Hi
I would do it with a policy from internal interface to public interface, from all internal addresses to an FQDN.
If this doesn't work because unfortunately on the IPv4 policy you can't have wildcard FQDNs, then I would have the IT guy make a web filter. Block all categories and then in the section called 'static URL filter' you can set URL overrides and put there FQDNs and wildcard FQDNs that are allowed to bypass the web filter.
If you need more details let me know.
Thank you for your reply. After some time looking into this I started to think it was impossible. Just to quickly check if I understood it correctly: There is a server in company's intranet or DMZ, behind a firewall. It's sole purpose is to respond to HTTP GET requests for resources from an app located in the cloud which has been given a URL like "myApp.mybluemix.net" and can be reached on that address. And the server can be blocked from any INCOMING connections but the connection from an app with that URL hosted in IBM cloud ? As in: firewall will filter connections INCOMING to intranet ? Or does it mean that the server will not be blocked from being accessed from the Internet, but it will be able to reply only to the App's URL because the firewall will block any other replies ? As in: firewall will filter connections OUTGOING to internet ? Cause we are concerned about security of server data, and the person managing firewall said second option may not be sufficiently secure and we would really like to have first option - blocking and filtering connection INCOMING to intranet.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1547 | |
1031 | |
749 | |
443 | |
210 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.