Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

PCI Compliance Certification and FortiManager

Posted on 2014-11-20
1
Medium Priority
?
208 Views
Last Modified: 2015-02-05
My company is in the final stages of acquiring a PCI Compliance certification.  We're one scanned tested away from obtaining this however the scans that are failing has traffic being directed to a FortiManager appliance.  The appliance is a VM, running on a Gen8 HP BL460 blade server with ESXi 5.0 as the Hypervisor.  Per Fortinet, the ports that are required to run are 22, 443, 6022, 6023, 53, 123, 514, 541, and 161.  Initially we had a full PAT from our external IP address to the internal IP address and so the vulnerability scan was picking up other vulnerabilities.  I setup firewall objects for each port and rewrote the policy to pass traffic on those ports only.  The scan comes back and and says that we're still failing on 22 and 443, which are secure, right?  Our FortiManager appliance is running at 5.0.6 currently.  There ARE newer versions of firmware which I'm not going to ignore as an option, but I want to be certain this is going to resolve my issue before spending the time to update the appliance.  Fortinet's technical support hasn't been much help, ironically, although I suspect the issue their is a matter of customer service, not intelligence.

Has anyone had to deal with PCI compliance and Fortinet Appliances?  Can someone tell me that fix for this is just to upgrade the appliance's firmware?  Any help would be appreciated.
0
Comment
Question by:Josef Al-Chacar
1 Comment
 
LVL 65

Accepted Solution

by:
btan earned 2000 total points
ID: 40457181
You need to see the error in specific to 22 and 443. The port does not mean secure and compliant, my take on possible area
a) clear traffic still go through like any other port though it should be implementing proper key exchange and encryption or even the expected protocol services
b) use of weak crypto cipher in 22 and 443
c) unpatched or vulnerable services in 22 and 443
d) trigger signature of exploits existence or matched in scanner db
e) false positive
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A new hacking trick has emerged leveraging your own helpdesk or support ticketing tools as an easy way to distribute malware.
2017 was a scary year for cyber security.  Hear what our security experts say that hackers have in store for us in 2018.
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data. But that feeling is fleeting. Attacks these days can happen in many w…
When cloud platforms entered the scene, users and companies jumped on board to take advantage of the many benefits, like the ability to work and connect with company information from various locations. What many didn't foresee was the increased risk…

564 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question