Q As_Round_1_16Jun2016.xls
XLS spreadsheet 56 KB Posted
- Solicitation number
- HC102816R0016
- Issued by
-
Defense Information Systems Agency
About this file
Q As Round 1 (Uploaded via Amendment dated 6/16/16)
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Revision_3_to_Attach_2__Salient_Characteristics.xlsx | XLSX spreadsheet | |
| Q As_Round_3_30June2016.xlsx | XLSX spreadsheet | |
| Atch_1_-_30Jun2016.xls | XLS spreadsheet | |
| Q As_Round_2_24June2016.xlsx | XLSX spreadsheet | |
| Revison_2_to_Atch_2_24Jun2016.xls | XLS spreadsheet | |
| Revison_1_to_Atch_2.xls | XLS spreadsheet | |
| Atch_1_-_EPL _MI RR _Price_Workbook.xls | XLS spreadsheet | |
| Atch_2_-_Salient_Characteristics.xlsx | XLSX spreadsheet | |
| Combined_Synopsis-Solicitation_Ltr_Palo_Alto_Firewalls_25May16.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Q&As Round 1 (Closed)
| Question # | Document | Description | Question/Clarification | Government Response |
| 1 | Atch 2 - Salient Characteristics.xlsx | All Models Tab - Content Inspection Requirements: |
27. All firewalls must perform L7 application identification at 90%+ of firewall rated performance under documented real-world (i.e. not UDP-only) traffic loads. The firewall must deny unknown traffic.
29. Verifiable throughput of mixed traffic type with all Firewall features turned on of a minimum of 60GB in a single chassis.
30. The firewall must perform threat inspection of known signatures at 50% of the firewall's rated throughput, while simultaneously maintaining 90%+ L7 performance
| 31. The firewall must be able to select files for forwarding, with negligible (<1%) performance impact), to a local appliance for unknown malware detection. It must also accept local signature insertion from that appliance into its threat database with turnaround time within 15 minutes. | During the evaluation, will the Navy require responders to validate “performance compliance" claims based on documented, real-world application traffic mix (e.g., not "UDP only" tests)? | Yes | |
| 2 | Atch 2 - Salient Characteristics.xlsx | All Models Tab - Content Inspection Requirements: | |
| 29. Verifiable throughput of mixed traffic type with all Firewall features turned on of a minimum of 60GB in a single chassis. | For evaluation purposes, does the Navy define the statement “all Firewall features turned on,” as simultaneous L7, AV, Spyware, and Vulnerability operation? | Each Model Tab has a throughput requirement defined. | |
| 3 | Atch 2 - Salient Characteristics.xlsx | All Models Tab: Items 26 and 29 are characteristics that are only supported on the 7050 model. These are incorrectly applied to all models. |
26. Must support a minimum of 8 each, 10 GB (line rate) connections in a single chassis
| 29. Verifiable throughput of mixed traffic type with all Firewall features turned on of a minimum of 60GB in a single chassis. | Items 26 and 29 in the All Models Tab should be moved to Model 1 Tab, which pertains to the 7050. | Items updated | |||
| 4 | Atch 2 - Salient Characteristics.xlsx | Model 2 Tab: Item 70 Performance Requirements for PA 5060 are incorrectly copied from Model 1 Salient characteristics for firewall PA 7050. | Per manufacturer specifications, this item should read as follows: 70. High performance NGFW (Next Generation Firewall). The configuration is flexible and able to handle multiple network connection types and speeds to include 1 and 10 Gig fiber, as well as 10/100/1000 Base-T in the same chassis. The NGFW is application aware with full stack visibility and full packet inspection. The NGFW supports Statefull High Availability. The chassis supports dual power supplies that are hot swappable. To ensure management access is always available, a separate control plane is used. The NGFW supports onboard logging with a minimum of 240GB, with options to offload/export system log files. | Model 2 tab updated | |
| 5 | Atch 2 - Salient Characteristics.xlsx | Model 3 Tab: Item 83 Performance Requirements for PA 3050 are incorrectly copied from Model 1 Salient characteristics for firewall PA 7050. | Per manufacturer specifications, this item should read as follows: 83. High performance NGFW (Next Generation Firewall). The configuration is flexible and able to handle multiple network connection types and speeds to include 1 Gig fiber, as well as 10/100/1000 Base-T in the same chassis. The NGFW is application aware with full stack visibility and full packet inspection. The NGFW supports Statefull High Availability. To ensure management access is always available, a separate control plane is used. The NGFW supports onboard logging with a minimum of 120GB, with options to offload/export system log files. | Model 3 tab updated | |
| 6 | Atch 2 - Salient Characteristics.xlsx | Model 3 Tab: Item 95. Redundant power supplies | Please remove Redundant Power Supplies from the description. This is not a characteristic of Model PA 3050. | Model 3 tab updated | |
| 7 | Atch 2 - Salient Characteristics.xlsx | Model 4 Tab: Item 96 Performance Requirements for PA 3020 are incorrectly copied from Model 1 Salient characteristics for firewall PA 7050. | Per manufacturer specifications, this item should read as follows: 96. High performance NGFW (Next Generation Firewall). The configuration is flexible and able to handle multiple network connection types and speeds to include 1 and 10 Gig fiber, as well as 10/100/1000 Base-T in the same chassis. The NGFW is application aware with full stack visibility and full packet inspection. The NGFW supports Statefull High Availability. The chassis supports dual power supplies that are hot swappable. To ensure management access is always available, a separate control plane is used. The NGFW supports onboard logging with a minimum of 120GB, with options to offload/export system log files. | Model 4 tab updated | |
| 8 | Atch 2 - Salient Characteristics.xlsx | Model 4 Tab: Item 108. Redundant power supplies | Please remove Redundant Power Supplies from the description. This is not a characteristic of Model PA 3020. | Model 4 tab updated | |
| 9 | Atch 1 - EPL MI RR, Price Workbook.xls | CLIN 0004AA description is incorrect. | Please update to match the correction made to Model 2: Item 70 Performance Requirements for PA 5060 on Atch 2 - Salient Characteristics worksheet | Concur | |
| 10 | Atch 1 - EPL MI RR, Price Workbook.xls | CLIN 0005AA description is incorrect. | Please update to match the correction made to Model 3: Item 83 Performance Requirements for PA 3050 on Atch 2 - Salient Characteristics worksheet | Concur | |
| 11 | Atch 1 - EPL MI RR, Price Workbook.xls | CLIN 0005 Performance Requirements | Please remove Redundant Power Supplies from the description. This is not a characteristic of Model PA 3050. | Concur | |
| 12 | Atch 1 - EPL MI RR, Price Workbook.xls | CLIN 0006AA description is incorrect. | Please update to match the correction made to Model 4: Item 96 Performance Requirements for PA 3020 on Atch 2 - Salient Characteristics worksheet | Concur | |
| 13 | Atch 1 - EPL MI RR, Price Workbook.xls | CLIN 0006 Performance Requirements | Please remove Redundant Power Supplies from the description. This is not a characteristic of Model PA 3020. | Concur | |
| 14 | Atch 2 - Salient Characteristics.xlsx | Model All Models Tab: Item 4. Management and data forwarding planes | This is a Palo Alto specific requirement. It is not clear what the specific issue is being addressed for example firewall up time or management interface access availability. I think this requirement should be removed. | Having a separate plane (processor, memory, and disk space) for management ensures that an administrator will always have access to the device in the event of a denial of service or other network event. Processing of network traffic will not have a negative impact on system management or logging. | |
| 15 | Atch 2 - Salient Characteristics.xlsx | Model All Models Tab: Item 19. Splunk App | This is a Palo Alto specific requirement. It is not clear what the specific issue sense merely having an app is the requirement. Requiring a firewall to integrate with Splunk is a measurable requirement. | Not Palo Alto specific. The firewall must be supported by Splunk via a vendor-specific Splunk App or Splunk Add-On http://www.splunk.com/en_us/products/apps-and-add-ons.html | |
| 16 | Atch 2 - Salient Characteristics.xlsx | Model All Models Tab: Item 54. DISA STIG | This is a Palo Alto specific requirement. Most follow industry best practice and RMF guidelines. | Not Palo Alto specific. Specific STIGs are available for several specific firewall vendors. | |
| 17 | Atch 2 - Salient Characteristics.xlsx | Model All Models Tab: Item 51. Auxiliary Port Lock | This is a Palo Alto specific requirement. This seems more like a optional requirement. Most installation keep this active for out of band management. | Not Palo Alto specific. This is a very common requirement for firewalls and most network devices. | |
| 18 | Atch 2 - Salient Characteristics.xlsx | Model Model 1, Model 2, Model 3, and Model 4 | The requirements as stated are merely copied from Palo Alto. Some of the key requirements are missed. 1. SSL Inspection throughput 2. IPS Throughput 3. Firewall Inspection Throughput 4. VPN throughput | The characteristics are Palo Alto or equivalent. | |
| 19 | Atch 2 - Salient Characteristics.xlsx | Model Model 1, Model 2, Model 3, and Model 4 | The hard drive requirement is a Palo Alto requirement. What do you want the firewall to do? An example would be to retain log files for 5 days in the event log collection server is offline. Some vendors use SSD drives for better performance. I think this requirement should be rewritten. | Hard drive requirement is for any vendor's firewall. | |
| 20 | Atch 2 - Salient Characteristics.xlsx | Model Model 1, Model 2, Model 3, and Model 4 | The AppIication ID throughput requirement is a Palo Alto requirement and represents the performance of turning on one feature. This feature is not representative of all the features that will be enable so it is a misleading statistic. This should be rewriten based on all the features you plan to utilize for example IPS, URL content filtering, spam, and AV. | The App ID (Layer 7) throughput is one of the many requirements for any vendor's firewall. | |
| 21 | Atch 2 - Salient Characteristics.xlsx | Model Model 1, Model 2, Model 3, and Model 4 | The port density requirements seem to based on what Palo Alto supports. The requirements step down the Polo Alto model line. These specs are normally based on usage like Data Center (High Density of ports), Boundary (lower density of high speed ports), Enclave firewall, etc | The port density is needed varies based on the use of the firewall (data center .vs. boundary, etc.) | |
| 22 | Atch 2 - Salient Characteristics.xlsx | Model Firewall MGT: #109 | These requirements are a cut and paste from Palo Alto instead of actual management requirements. The requirement to mange up to 100 devices is what dictates how much storage a vendor needs. The requirement on 4TB should be removed. | The management console must be purpose-built for the management of up to 100 firewalls and have 4TB minimum of RAID storage. | |
| 23 | Atch 2 - Salient Characteristics.xlsx | Model Firewall MGT | Why is a Mobile device requirement placed on the firewall management? This seems totally out of place. | Not Firewall MGT. This is listed under Accessories and Services. | |
| 24 | Atch 2 - Salient Characteristics.xlsx | Model Firewall MGT: #110 | This requirement should be Panorama or equivalent. | Changed to read Panaorma or equivalent. | |
| 25 | Atch 1 - EPL MI RR, Price Workbook.xls | CLIN 0016, PAN-GP-100 | This CLIN/part number is end-of-life with Palo Alto. Can we leave the SKU off the response? | Yes. | |
| End of Q&As Round 1. For *NEW* quesitons, due on 6/20/2016, please use the workbook's tab bewow titled "Q&A Round 2" |
Q&As Round 2 (due 6-20-2016) Question # Document Description Question/Clarification Government Response
File details come from the government source that posted it. Updated .