Loading…
India Infra Updates on WhatsApp
Join the Tenderkart WhatsApp channel for India Tender Updates
Loading…
Tender ID
Eligibility, documents, scope and key termsEligibility, required documents, scope of work and key terms of this tender, in one click.
Tender Value
Refer Docs
Closing Date
14 Nov 2023, 11:59 pmClosed
Eligibility, documents, scope and key termsEligibility, required documents, scope of work and key terms of this tender, in one click.
Contracts & Procurement Department
Odisha
RC for SITC of DDOS and WAF in TPCODL, TPNODL, TPWODL and TPSODL
TPCODL-CCG-23-24--041
TPCODL/CCG/23-24/041
Open Tender
sitc
Tender Notice
Odisha
TP Western Odisha Distribution Limited (TPWODL)
Yes
Online / as specified in tender document
14 Nov 2023
20 Nov 2023
16 Oct 2023
S. NO Clause No Product Clause Change Requested/Suggestion/Clarification Justifications Remarks
1 3 DDOS The Proposed solution should be a Dedicated appliance (NOT a part of Router,UTM, Application Delivery Controller,Proxy based architecture or any StateFul Appliance). The Proposed solution should be a Dedicated appliance (NOT a part of Router,UTM, Application Delivery Controller,Proxy based architecture or IPS or any StateFul Appliance). IPS is missing out of this. IPS are layer 2 devices which works on signatures and should be from a different oem to have a multi layer security architecuture. Request you to ammend the clause as suggested. This clause to be read as "The Proposed solution should be a dedicated hardware appliance"
2 4 DDoS Flood Attack Prevention Rate: 25MPPS (In addition to Legitimate throughput) DDoS Flood Attack Prevention Rate: 25MPPS (In addition to Legitimate throughput) scalable to 35 mpps In terms of asked thropughpt scalability mpps scalability should be available with the appliance to avoid any future replacement of appliance for upgrade purposes. This should be given either as scalable or from day 1 This clause to be read as "DDoS Flood Attack minimum Prevention Rate: 25MPPS"
Mitigation Throughput: 20Gbps request to remove this Attack size cant be defined. We do not mention the mitigation size as the practicality is legitimate throughput irrespective of the attack size. As asked 2 Gbps of clean traffic always will be given back protecting 20 or 40 gbps of attack size. This clause to be read as "Solution must provide 2 Gbps clean traffic from day 1 and scalable to upto 12Gbps. Capable to handle attack size minimum 20 Gbps from day 1"
Legitimate throughput handling: 2Gbps from day-1 and scalable upto 12Gbps Legitimate throughput handling: 2Gbps from day-1 and scalable upto 20Gbps with web 3.0/4.0 the internet bandwidths will be going way high then the asked. 20 Gbps will be supporting a bandwidth of 10 Gbps in future which will be a normal scalability ask, Else the appliance replacement will be required. Request you to increase the scalability asked. This clause to be read as "Solution must provide 2 Gbps clean traffic from day 1 and scalable to upto 12Gbps. Capable to handle attack size minimum 20 Gbps from day 1"
Attack Concurrent Sessions : Unlimited
Inspection Ports: 4 x 10 SFP+ and 8 x 1G SFP Inspection Ports: 4 x 10 SFP+ and 8 x 1G SFP supporting internal bypass for sofware and hardware failure on all the inspection interfaces to achieve faster network convergence in High Availability/Resilient Deployment Being an inline layer 2 device in case any failure with the device occurs it should have capability to bypass the device to keep the production running. Tender clause stands
Latency should be less than 80 microseconds. Tender clause stands
The appliance should have dedicated 2 x 1G RJ45 Out-of-band Management Port and RJ45 Console Port Tender clause stands
* Data should be publically available In case the solution is capable but specification is not available in public then bidder should submit the acceptance from OEM by dully signed and stamped on OEM letter head. All the technical complance need to be submit on OEM letter head by the bidder.
3 6 BEHAVIORAL ANALYSIS using behavioral algorithms and automation to defend against IoT botnet threats, including Mirai DNS Water Torture, Burst and Randomized attacks. The solution should utilize behavioral algorithms and stateless solution to detect and defend against threats at L3-7. BEHAVIORAL ANALYSIS using behavioral algorithms/challange-response/http authentication to defend against IoT botnet threats, including Mirai DNS Water Torture, Burst and Randomized attacks. The solution should utilize behavioral algorithms/challange response/http authentication and stateless solution to detect and defend against threats at L3-7. OEM specific language as every oem has its own way of preventing the attacks. This clause to be read as "BEHAVIORAL ANALYSIS using behavioral algorithms/challange-response/http authentication to defend against IoT botnet threats, including Mirai DNS Water Torture, Burst and Randomized attacks. The solution should utilize behavioral algorithms/challange response/http authentication and stateless solution to detect and defend against threats at L3-7."
4 7 Behavioral DoS (Behavioral Denial of Service) Protection should defend against zero-day network-flood attacks, detect traffic anomalies and prevent zero-day, unknown, flood attacks by identifying the footprint of the anomalous traffic. Behavioral DoS (Behavioral Denial of Service) Protection/challenge response/http auth should defend against zero-day network-flood attacks, detect traffic anomalies and prevent zero-day, unknown, flood attacks by identifying the footprint of the anomalous traffic. OEM specific language as every oem has its own way of preventing the attacks. This clause to be read as "BEHAVIORAL ANALYSIS using behavioral algorithms/challange-response/http authentication to defend against IoT botnet threats, including Mirai DNS Water Torture, Burst and Randomized attacks. The solution should utilize behavioral algorithms/challange response/http authentication and stateless solution to detect and defend against threats at L3-7."
Network-flood protection should include:
• TCP floods—which include SYN Flood, TCP Fin + ACK Flood, TCP Reset Flood, TCP SYN + ACK Flood, and TCP Fragmentation Flood
5 9 Positive Security Model should have advanced behavior-analysis technologies to separate malicious threats from legitimate traffic Positive Security Model should have advanced behavior-analysis/challenge response/http authentication technologies to separate malicious threats from legitimate traffic OEM specific language as every oem has its own way of preventing the attacks. This clause to be read as "Positive Security Model should have advanced behavior-analysis/challenge response/http authentication technologies to separate malicious threats from legitimate traffic"
6 13 System should support In-Line, SPAN Port, Out-of-Path deployment modes from day 1. The proposed device should also support 5000+ inbuilt Signatures apart from custom Signatures from Day 1. System should support In-Line, SPAN Port, Out-of-Path deployment modes from day 1. The proposed device should also support 5000+ inbuilt Signatures/IOCs apart from custom Signatures from Day 1. DDOS solutions works on the IOCs where signature r are part of IPS/FW devices. We being the global leader in DDOS do specific research on the DDOS IOCs which are not limited to 5k but are approx 1 million. Tender clause stands
7 16 The appliance should have below Security Protection Profiles: The appliance should have the capability to create multiple security protection profile groups to protect different type of server types by creating different granular countermeasures for them. OEM specific names, however it should have the granularity to create different groups of servers like ftp, dns , web for their specific thresholds etc This clasue to be read as solution must provide proetection against following types of attacks: 1. Challenge Response/BDoS Protection. 2. DNS Protections. 3. SYN-Flood Protection. 4. Traffic Filters. 5. Out-of-State Protection There are different kinds of attacks which falls under DDoS attack, in order to mitigate these attacks vendor should have dedicated security engines. This is minimum technical requirement. Bidders may provide better or more options accordingly.
1. BDoS Protection.
2. DNS Protections.
3. SYN-Flood Protection.
4. Traffic Filters.
5. Out-of-State Protection
8 20 The solution should provide Geo-Location blocking, Active Attacker Feeds and Signature Update Service from day-1 The solution should provide Geo-Location blocking, Active Attacker Feeds and Signature/IOC Update Service from day-1 DDOS solutions works on the IOCs where signature r are part of IPS/FW devices. We being the global leader in DDOS do specific research on the DDOS IOCs which are not limited to 5k but are approx 1 million. Tender clause stands
9 21 For future Use: The solution should support Integration with OEM own Cloud based Scrubbing Centers in case of Bandwidth Saturation attacks. The solution should support Integration with cleanpipe service of atleast 4 ISPs in India and OEM own Cloud based Scrubbing Centers in case of Bandwidth Saturation attacks where DDOS appliance should support cloud singalling to singal upstream ISP to start the mitigation in case of saturation attacks. cloud based is not a practical solution as that requires customer to own their /24 subnet from ISP along with the BGP AS to route the traffic to any cloud in case of an attack. Customers use cleanpipe service where this routing is not required and in case of attack is seen by the on prem ddos it sends the singal back to the ISP cleanpipe for starting the mitigation. This should be available from day 1 as that is very important aspect and is required to protect against major volumetric ddos attack. This clause to be read as "For future use: The solution should support Integration with Cloud based OEM own Scrubbing Centers in case of Bandwidth Saturation attacks. "
10 DDOS Missing Important Clause Pls add the clause as " Supports over 3 Million IOC Blocking via integration with 3rd Party TIP" next gen DDOS supports protection to the first entry to the organization and the last exit for the internal network. Where it should support millions IOCs via third party platforms integrations for the most effective security framwork and protection. CERT-IN too provides IOCs for the same purposes where that integration should be supported by all the security devices No change in clause. This is minimum technical requirement. Bidders are free to quote additional features.
11 DDOS Missing Important Clause Pls add the clause as " The proposed system must support automatic cloud signalling to signal to upstream ISPs or managed service provider who is providing anti-DDoS cloud service for very large DDoS attack mitigation." It is important for organization to have Automatic Cloud Signaling between On-Premise and Cloud Scrubbing Service. In this context organization should have flexibility to choose from maximum possible ISP that support Automatic Cloud Signaling with On-Premise appliance rather than be restricted to few ISP/MSSP No change in clause. This is minimum technical requirement. Bidders are free to quote additional features.
12 DDOS Missing Important Clause Pls add the clause as " OEM Anti-DDoS Solution should be deployed and used by at least 4 Tier 1 (class A) Internet service providers (ISPs) in India to protect their own Core infrastructure from DDoS attacks" as the bandwidth is provided by the ISPs where scrubbing should be possible at the ISP front which are Teir 1 ISPs in India to have the volumetric layer 4 attacks at their level itself. It is always recommended to have clean pipe from ISP and on prem devices to block the attacks upto layer 7. No change in clause. This is minimum technical requirement. Bidders are free to quote additional features.
13 DDOS Please add the clause as " System should have capability to consume and integrate with 3rd Party feeds (IOCs) via STIX/TAXII inbuilt integration capability . STIX/TAXII are open standards to get the feeds for more richness of security devices and is openly supported by the security OEMs. This is a must to have function for any security device and is also supported by CERT-IN for providing their IOCs/Feeds which can be automatically ingested using STIX TAXII. No change in clause. This is minimum technical requirement. Bidders are free to quote additional features.
14 ANNEXURE II Technical Specifications DDOS; Clause No 4; page No 20 DDOS DDoS Flood Attack Prevention Rate: 25MPPS (In addition to Legitimate throughput) Mitigation Throughput: 20Gbps Legitimate throughput handling: 2Gbps from day-1 and scalable up to 12Gbps Attack Concurrent Sessions : Unlimited Inspection Ports: 4 x 10 SFP+ and 8 x 1G SFP Latency should be less than 80 microseconds. The appliance should have dedicated 2 x 1G RJ45 Out-of-band Management Port and RJ45 Console Port * Data should be publically available DDoS Flood Attack Prevention Rate: 25MPPS System Throughput: 40Gbps Ports: 8 x 10 SFP+ and 4 x 1GbE SFP Bypass port. Management: SSH CLI, Direct Console DB9 CLI, SNMP, Single Console per Cluster, XML-RPC, Out of Band Management – RJ45/DB9 * Data should be publically available Very important bypass port was missing, along with some important parameters for management. And in Datacentre enviourment 10G port with backward compatibility is strongly suggested over 1G. So, We would like to Request the Honourable tendering committee to amend the clause as requested. Please refer amended clause no. 4 above
15 ANNEXURE II Technical Specifications DDOS; Clause No 6; page No 20 DDOS BEHAVIORAL ANALYSIS using behavioural algorithms and automation to defend against IoT botnet threats, including Mirai DNS Water Torture, Burst and Randomized attacks. The solution should utilize behavioural algorithms and stateless solution to detect and defend against threats at L3-7. BEHAVIORAL ANALYSIS using behavioural algorithms and automation to defend against IoT botnet threats. And DNS DDoS Mitigation. The solution should utilize behavioural algorithms and stateless solution to detect and defend against threats at L3-7. Different OEM has different terminology for similar functions. So, We would like to Request the Honourable tendering committee to amend the clause as requested for wider participation. Please refer amended clause no. 6 above
16 ANNEXURE II Technical Specifications DDOS; Clause No 12; page No 21 DDOS System should have SIP Flood Protection, UDP and UDP Fragmented Flood. The system should have TCP/UDP/ICMP DDoS mitigation : TCP SYN Flood, TCP SYN-ACK Flood, TCP ACK Flood, TCP FIN/RST Flood, TCP Connection Flood, TCP Fragment Flood, TCP Slow Connection, TCP Abnormal Connection Please amend the clause to protect from most common and widely used DDOS attacks. No change in clause. This is minimum technical requirement. Bidders are free to quote additional features.
17 ANNEXURE II Technical Specifications DDOS; Clause No 13; page No 21 DDOS System should support In-Line, SPAN Port, Out-of-Path deployment modes from day 1. The proposed device should also support 5000+ inbuilt Signatures apart from custom Signatures from Day 1. System should support In-Line/Bridge mode, SPAN Port/TAP mode, Out-of-Path deployment modes from day 1. System should have capability to allow custom signature creation apart from inbuilt signatures 3000 from day 1. We would like to Request the Honourable tendering committee to amend the clause as different OEM use different terminology for same function and quality of the signature is more important than the number of signatures. No change in clause. This is minimum technical requirement. Bidders are free to quote additional features.
18 ANNEXURE II Technical Specifications DDOS; Clause No 16; page No 21 DDOS The appliance should have below Security Protection Profiles: 1. BDoS Protection. 2. DNS Protections. 3. SYN-Flood Protection. 4. Traffic Filters. 5. Out-of-State Protection The appliance should support Dynamic profiling, Automatic DDoS profile, Manual DDoS Profile, Application & network DDoS profile, Dynamic refreshing of automatic DDoS profile based on learning results. Different OEM has different profile types and names. So, We would like to Request the Honourable tendering committee to use generic terminology to cover all type of profiling and amend the clause as requested for wider participation. Please refer amended clause no. 16 above
52 DDOS DDoS Flood Attack Prevention Rate: 25MPPS (In addition to Legitimate throughput) Mitigation Throughput: 20Gbps Legitimate throughput handling: 2Gbps from day-1 and scalable upto 12Gbps Attack Concurrent Sessions : Unlimited Inspection Ports: 4 x 10 SFP+ and 8 x 1G SFP Latency should be less than 80 microseconds. The appliance should have dedicated 2 x 1G RJ45 Out-of-band Management Port and RJ45 Console Port * Data should be publically available DDoS Flood Attack Prevention Rate: 25MPPS (In addition to Legitimate throughput) Mitigation Throughput: 20Gbps Legitimate throughput handling: 2Gbps from day-1 and scalable upto 12Gbps > To be Deleted Attack Concurrent Sessions : Unlimited Inspection Ports: 4 x 10 SFP+ and 4 x 1G SFP Latency should be less than 80 microseconds. The appliance should have dedicated 2 x 1G RJ45 Out-of-band Management Port and RJ45 Console Port * Data should be publically available In the Specific clause you have already asked for maximum mitigation throughput and MPPS are also asked. You may not require a separate Legitimate throughput and this parameter might not be available in all OEM public datasheets. Below point need to be removed " Legitimate throughput handling: 2Gbps from day-1 and scalable upto 12Gbps " . Also you will not have more than 4 ISPs and 8 ports in total (4*10G and 4*1G ) are sufficient to be asked in RFP Please refer amended clause no. 4 above
53 DDOS System should support horizontal and vertical port scanning behavioral protection. To be Deleted This point is related to IPS. Anways the same has been asked in both Internal and Perimeter firewall. This point is favoring RADWARE as they provide IPS in their DDOS Tender clause stands
54 DDOS System should support In-Line, SPAN Port, Out-of-Path deployment modes from day 1. The proposed device should also support 5000+ inbuilt Signatures apart from custom Signatures from Day 1. System should support In-Line, SPAN Port, Out-of-Path deployment modes from day 1 This point is related to IPS. Anways the same has been asked in both Internal and Perimeter firewall. This point is favoring RADWARE as they provide IPS in their DDOS No change in clause. This is minimum technical requirement. Bidders are free to quote additional features.
55 DDOS For future Use: The solution should support Integration with OEM own cloud based Scrubbing Centers in case of Bandwidth Saturation attacks. For future Use: The solution should support Integration with OEM own cloud/Integration with Third Party based Scrubbing Centers in case of Bandwidth Saturation attacks. Every OEM might not have their own scrubbing centers but they have integration/joint venture model with third party and provide more strength in mitigating the attacks as compared to other vendors This clause to be read as "For future use: The solution should support Integration with Cloud based OEM own Scrubbing Centers in case of Bandwidth Saturation attacks. "
56 DDOS Bidder should propose Separate Centralized Management & Reporting Solution from Day 1. Bidder should propose Centralized Management/local Web UI to manage the appliance & additional Reporting Solution from Day 1. Local WebUI option must be provided as this is more easy option to manage. Tender clause stands
57 DDOS System should support horizontal and vertical port scanning behavioural protection or System should protect against port scanning of vulnerable services on a system, and mitigate DoS attacks, Different OEM has different terminology for similar functions. So, We would like to Request the Honourable tendering committee to amend the clause System should support horizontal and vertical port scanning behavioural protection or System should protect against port scanning of vulnerable services on a system, and mitigate DoS attacks. Please remove this point To wider participation of bidder, please remove this point, Tender clause stands
58 DDOS Clause can be read as "Positive Security Model should have advanced behavior- analysis/challenge response/http authentication technologies to separate malicious threats from Please remove this point To wider participation of bidder, please remove this point, Tender clause stands
59 DDOS This clause can be read as "System should support DNS Challenge/DNS Source Verification and DNS Rate Limit" Please remove this point To wider participation of bidder, please remove this point, Tender clause stands
60 DDOS "System should support HTTP Challenge Response authentication without Scripts/client authentication" Please remove this point To wider participation of bidder, please remove this point, Tender clause stands
61 DDOS Sufficient number of signature is very important to address known attacks. The asked deployment mode is minimum requirement. Clause Amended. Clause can be read as "System should support In- Line/Bridge, SPAN Port/TAP Mode, Out-of-Path deployment modes from day 1. The proposed device should also support 5000+ inbuilt Please remove this point To wider participation of bidder, please remove this point, Tender clause stands
62 DDOS This clasue to be read as solution must provide proetection against following types of attacks: 1. BDoS Protection. 2. DNS Protections. 3. SYN-Flood Protection. 4. Traffic Filters. 5. Out-of-State Protection There are different kinds of attacks which falls under DDoS attack, in order to mitigate these attacks vendor should have dedicated security engines. This is minimum technical requirement. Bidders may provide Please remove this point To wider participation of bidder, please remove this point, Tender clause stands
Sl. No. Section No. Clause No. Page No. RFP Clause Queries/Change Request Clarification Remarks
6 ANNEXURE II Technical Specifications WAF 1 22 Proposed hardware platform should be of high performance, highly scalable, and purpose-built next Generation platform for application security with integrated functionalities of Application Load Balancer and Web Application Firewall (WAF) from same OEM running on same OEM OS version and platform; Web Application solution should not be virtual WAF and it should not white labeled WAF running on third party hardware. Proposed hardware platform should be of high performance, highly scalable, and purpose-built next Generation platform for application security. Web Application solution should not white labeled WAF running on third party hardware. This clause is specific to OEM who has supplied application load balancer to your esteemed organization. Also let us know whether we have to consider application load balancer with WAF while preparing BoM. Tender clause stands Bidder can propose multiple appliances for the solution.
7 ANNEXURE II Technical Specifications WAF 9 24 The software solution must support Programmability to support Automation, native integration and orchestration. It should enable declarative provisioning and configuration of the software solution across cloud environments and integration withautomation and CI/CD tools including Ansible, Jenkins, and Terraform. The software solution must support Programmability to support Automation using XML-RPC, RESTful API. Ansible, terraform, & Jenkins Pipeline are suite of plugins, and mainly used for software coding and testing purpose. We would like to request the tendering committee to amend the clause as requested for wider participation. Tender clause stands
8 ANNEXURE II Technical Specifications WAF 10 24 Should support virtualization with its own hypervisor (NOT any third party or open source) that virtualizes the Device resources—including CPU, memory, management and configuration. The proposed device should have 8 Virtual Instances from Day 1 scalable to 20 using license upgrade. Should support virtualization with its own hypervisor (NOT any third party or open source) that virtualizes the Device resources—including CPU, memory, management and configuration. The proposed device should have 8 Virtual Instances from Day 1,scalable to 32 without any additional license. We would like to request the tendering committee to amend the clause as requested to get better flexibility and best techno-commercial product available in the market. Tender clause stands
9 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 1 24 The Web Application Firewall shall have integration with REDHAT OpenShift Kubernetes Platforms and requisite controller/license/container plugin shall be provided with WAF solution from day one. Controller/Plug-in should be from same make as WAF. It should not be third party or opensource. WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
10 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 2 24 The Controller/Container Plugin shall support both Nodeport and ClusterIP mode of deployment and also as an Ingress service. WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
11 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 3 24 The Controller/Container Plugin shall support Application Delivery Controller orchestration to dynamically create and manage WAF objects. WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
12 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 4 24 The Controller/Container Plugin shall support PER NAMESPACE operations with the capability to run Ingress service plugins on a PER NAMESPACE basis WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
13 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 5 24 The Web Application Firewall shall be capable to forward traffic to container cluster via NodePort and ClusterIP. WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
14 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 6 24 The Controller/Container Plugin shall support the configuration of advanced services like Web application firewalls through declarative syntax. WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
15 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 7 25 The Controller/Container Plugin shall support integration using latest Container network interface (CNI) for the container platform. WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
16 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 8 25 The Web Application Firewall shall support NodePort mechanism for integration with kubernetes services. WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
17 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 9 25 The Web Application Firewall shall support BGP for integration with kubernetes services. WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
18 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 10 25 The Web Application Firewall shall support overlay network like VxLAN/Geneve for integration with kubernetes services WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
19 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 11 25 WAF should integrates with REDHAT Openshift container orchestration environments to dynamically create L4/L7 services on WAF, and load balance network traffic across the services. Monitoring the orchstration API server, Solution should be able to modify the WAF configuration based on changes made to containerized applications. WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
20 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 12 25 Installation of Controller/Container Plugin should be using Operators on OpenShift Cluster and Helm charts. WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
21 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 13 25 Controller/Container Plugin should use open shift route resources and support route annotations. WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
22 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 14 25 Controller/Container Plugin should use multiple Virtual IP addresses WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
23 ANNEXURE II Technical Specifications WAF Native and Kubernetes integration Features: 15 25 Controller/Container Plugin should use Custom resources extensions of the Kubernetes API. It should registers to the Kubernetes client-go using informers to retrieve Virtual Server, TLSProfile, Service, Endpoint and Node create, update, and delete events. Resources identified from such events are pushed to a Resource Queue maintained by controller. WAF solution for REDHAT Openshift Kubernetes & Traditional infra based applications are totally different in nature and required different solutions to address the requirement. As per the RFP specification Point 4 to 10 TPCODL is looking for Appliance based WAF solution which is not sufficient to serve independently for this two different platforms and required additional BOQ line items/solution, and inclusion of point no "WAF Native and Kubernetes integration Features: point 1" making the WAF technical specification OEM specific. So we would like to request the honourable tendering committee to separate this two solutions/Requirement. This clause is restricting us to participate. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
24 ANNEXURE II Technical Specifications WAF Web Application Firewall Solution Functional Requirements: 2 25 The Web Application Firewall Solution shall support the following Load Balancing Features Support for 200 servers Support load balancing algorithms Least connection Ratio Round Robin weighted Least connection The Web Application Firewall Solution shall support the following Load Balancing Features Support for 200 servers Support load balancing algorithms Least connection Round Robin weighted Least connection OEM specific terminology, We would like to request the tendering committee to amend the clause as requested for wider participation. Tender clause stands
25 ANNEXURE II Technical Specifications WAF Web Application Firewall Solution Functional Requirements: 4 26 The Web Application Firewall Solution shall be able to learn the Web Application Structure & elements to address the difficulty of configuring the positive security model. The Web Application Firewall Solution should have APPLICATION SECURITY VISIBILITY to address the difficulty of configuring the positive security model. Different OEM has different terminology for similar functions. So, We would like to Request the Honourable tendering committee to amend the clause as requested for wider participation. Tender clause stands
26 ANNEXURE II Technical Specifications WAF Web Application Firewall Solution Functional Requirements: 5 26 The Web Application Firewall Solution in learning mode shall be able to recognize application changes while simultaneously protecting Web applications and learned values shall be used as the configuration for input checking in the positive security model. The Web Application Firewall Solution should automatically learn the normal traffic to form positive whitelist and refresh the WAF profile dynamically. Different OEM has different terminology for similar functions. So, We would like to Request the Honourable tendering committee to amend the clause as requested for wider participation. Tender clause stands
27 ANNEXURE II Technical Specifications WAF Web Application Firewall Solution Functional Requirements: 11 28 The Web Application Firewall Solution shall be able to prevent automated layer 7 DDoS attacks, web scraping, and brute force attacks from being directed to the site. The Web Application Firewall Solution shall be able to prevent automated layer 7 DDoS attacks, bot, and brute force attacks from being directed to the site. Different OEM has different terminology for similar functions. So, We would like to Request the Honourable tendering committee to amend the clause as requested for wider participation. Tender clause stands
28 ANNEXURE II Technical Specifications WAF Web Application Firewall Solution Functional Requirements: 12 28 The Web Application Firewall Solution shall have "anti-automation" protection which can block the automated attacks using hacking tools, scripts, frameworks, etc. The Web Application Firewall Solution shall have protection from automated attacks using hacking tools, scripts, frameworks, etc. Different OEM has different terminology for similar functions. So, We would like to Request the Honourable tendering committee to amend the clause as requested for wider participation. Tender clause stands
29 ANNEXURE II Technical Specifications WAF Web Application Firewall Solution Functional Requirements: 19 28 The Web Application Firewall Solution shall support integration with VA scanning tools to imports the XML report and provide a quick fix of the vulnerabilities including Acunetix, Qualys, Rapid 7, IBM Appscan etc. to virtually patch web application vulnerabilities. The Web Application Firewall Solution shall support integration with VA scanning tools to virtually patch web application vulnerabilities. The requirement is integration with third-party VA tools for virtual patching, We would like to Request the Honourable tendering committee to amend the clause as requested. Tender clause stands
30 ANNEXURE II Technical Specifications WAF Web Application Firewall Solution Functional Requirements: 33 30 The solution should provide OWASP Compliance Dashboard which provides holistic and interactive interface that clearly measures app's compliancy against the OWASP Application Security Top 10 and also provide suggestions/shortcuts to address the compliances and configure policies for it. The solution should provide protection from OWASP top 10 attacks. We would like to Request the Honourable tendering committee to amend the clause as requested for wider participation. This clause to be read as "The solution should provide OWASP Dashboard which provides holistic and interactive interface that clearly measures app's compliancy against the latest OWASP Application Security Top 10 and also provide suggestions/shortcuts to address the compliances and configure policies for it."
31 ANNEXURE II Technical Specifications WAF Management & Reporting 4 31 The solution should provide online troubleshooting and traffic analysis tool where the administrator can take a snapshot of the config and upload it on web based diagnostic tool to check the health and vulnerability of the solution with the recommended solution provided on the knowledge base link. The solution should provide online troubleshooting and traffic analysis tool where the administrator can take a snapshot of the config and upload it on web based diagnostic tool to check the health and vulnerability of the solution with the recommended solution provided on the knowledge base link or Via TAC Support. Different OEM has different approach to achieve similar functions. So, We would like to Request the Honourable tendering committee to amend the clause as requested for wider participation. This clause to be read as "The solution should provide online troubleshooting and traffic analysis tool where the administrator can take a snapshot of the config and upload it on web based diagnostic tool to check the health and vulnerability of the solution with the recommended solution provided on the knowledge base link or Via TAC Support."
32 ANNEXURE II Technical Specifications WAF Management & Reporting 5 31 WAF should provide the application visibility and reporting with the below metrics and entity for each application: • Client IP addresses/subnets as well as geographical regions • Total Transactions as well as Average and Max Transactions/sec • Most commonly requested URLs • Server Latency and Page Load times • Virtual Server and Pool server performance • Page Load Time • Response code • OS and Browser • URL details WAF should provide the application visibility and reporting with the below: • Providing rich event logs to facilitate the replay and audit of attacks. • Providing WAF attack logs, WAF audit logs, HTTP access logs. DDoS warning logs, DDoS attack logs and HTTP filter logs • Supporting admin audit logs to facilitate the auditing against administrators. • Supporting exporting security event logs. • Providing granular and intuitive graphic monitoring. • Displaying system status such as CPU usage, RAM usage, disk usage and throughput. • Displaying attack statistics, covering severity distribution, attack type, attack sources, attack source regions and so on. • Displaying service traffic statistics, including detailed statistics for the traffic of different protocols. • Displaying packet drop statistics including the drop reason statistics. • Displaying service access statistics, including the TopN accessed URLs, client IPs and so on. • Supporting custom monitoring pages by adding desired monitoring graphs. • Supporting exporting monitoring graphs manually and generating monitoring report periodically. • Supporting generating one-time or periodic advanced reports. • Supporting system status reports, application security status report, PCI DSS compliance reports and so on. We would like to Request the Honourable tendering committee to amend the clause as requested with generic and in detail matrix for betterment of the solution and wider participation. Tender clause stands
33 ANNEXURE II Technical Specifications WAF User’s access for management. 4 31 The management server must support the archiving and it shall be able to export logs/events using NFS/SMB/SCP/SFTP. The management server must support the archiving and it shall be able to export logs/events. Different OEM has different approach to achieve similar functions. So, We would like to Request the Honourable tendering committee to amend the clause as requested for wider participation. Tender clause stands
34 ANNEXURE II Technical Specifications WAF User’s access for management. 7 32 The Web Application Firewall shall generate alarms w.r.t. health status of Server/s, security alarms for TCP SYN attacks, DoS attacks, etc. The Solution can provide Server health status and security alarms for TCP SYN attacks, DoS attacks, etc. Different OEM has different approach to achieve similar functions. So, We would like to Request the Honourable tendering committee to amend the clause as requested for wider participation. Tender clause stands
35 ANNEXURE II Technical Specifications WAF Product / OEM Evaluation Criteria 1 33 WAF / WAF’s Operating System should be tested and certified for EAL 2 / NDPP (Network Device Protection Profile)/NDcPP (Network Device collaborative Protection Profile) or above under Common Criteria Program for security related functions or under Indian Common Criteria Certification Scheme (IC3S) by STQC, MeitY, Govt. of India. WAF / WAF’s Operating System should be tested and certified for EAL 2 /ICES-003/ NDPP (Network Device Protection Profile)/NDcPP (Network Device collaborative Protection Profile) or above under Common Criteria Program for security related functions or under Indian Common Criteria Certification Scheme (IC3S) by STQC, MeitY, Govt. of India. We would like to Request the Honourable tendering committee to amend the clause as requested for wider participation. Tender clause stands
36 ANNEXURE II Technical Specifications WAF Product / OEM Evaluation Criteria 2 33 The WAF solution should be in the Gartner's Magic Quadrant of Latest published Gartner Report “Web Application and API Protection” The WAF solution should be in the Gartner's Magic Quadrant of Latest published Gartner Report or ICSA lab Certified. We would like to Request the Honourable tendering committee to amend the clause as requested for wider participation. Tender clause stands
37 ANNEXURE II Technical Specifications WAF High Availability 2 33 Should support transparent failover between 2 devices, the failover should be transparent to other networking devices with SSL session mirroring. Should support transparent failover between 2 devices, the failover should be transparent to other networking devices. Different OEM has different approach to achieve similar functions. So, We would like to Request the Honourable tendering committee to amend the clause as requested for wider participation. Tender clause stands
38 Technical Specification for WAF , Page 22 , Serial Number 1 Proposed hardware platform should be of high performance, highly scalable, and purpose-built next Generation platform for application security with integrated functionalities of Application Load Balancer and Web Application Firewall (WAF) from same OEM running on same OEM OS version and platform; Web Application solution should not be virtual WAF and it should not white labeled WAF running on third party hardware. This category is for WAF Solution, we as Imperva provides Purpose built WAF and we don,t have any ADC / LB feature, we are pioneer of WAF Solutiona and leaders in this category but we are non-complied against many clauses becasue lots of ADC features have been asked under WAF category. we would request you to kindly modifySince the ask in the RFP is of a WAF we request you to modify the cluase to - Proposed hardware platform should be of high performance, highly scalable, and purpose-built Web Application Firewall. Web Application solution should not be virtual WAF and it should not white labeled WAF running on third party hardware. Tender clause stands
39 Technical Specification for WAF , Page 23 , Solution Capabilities, Serial Number 2 The Web Application Firewall Solution shall have minimum 50 Million concurrent TCP connections. The WAF sizing is done on throughput that you have already mentioned in an earlier clause. That metric is what is need to size the WAF. The concurrent TCP Connections is not something on which WAF is sized and hence is not mentioned in any Datasheet of purpose built WAF. We would request you to kindly remove this clause. Tender clause stands
40 Technical Specification for WAF , Page 23 , Solution Capabilities, Serial Number 3 The Web Application Firewall Solution shall have minimum 04 Lakh L4 TCP connections / second. The WAF sizing is done on throughput that you have already mentioned in an earlier clause. That metric is what is need to size the WAF. The number of TCP Connections is not something on which WAF is sized and hence is not mentioned in any Datasheet of purpose built WAF. We would request you to kindly remove this clause. Tender clause stands
41 Technical Specification for WAF , Page 23 , Solution Capabilities, Serial Number 4 The Web Application Firewall Solution shall have minimum 10 Million HTTP request / second. The WAF sizing is done on throughput that you have already mentioned in an earlier clause. That metric is what is need to size the WAF. The number of HTTP request/second is not something on which WAF is sized and hence is not mentioned in any Datasheet of purpose built WAF. We would request you to kindly remove this clause. Tender clause stands
42 Technical Specification for WAF , Page 23 , Solution Capabilities, Serial Number 5 The WAF shall support minimum 60,000 RSA and 30,000 ECC SSL transactions per second. SLL TPS rating specify the number of new SSL connections (Key exchanges) per second without session key reuse. The amount of traffic that WAF will have to process wont need 60,000 keys. These values are too high and only supported by ADC Vendors. We reuqest you to change it to a value so that purpose build WAF vendors can also comply. We would request you to kindly modify the clause as below:- The WAF shall support minimum 22,000 RSA OR 30,000 ECC SSL transactions per second. SLL TPS rating specify the number of new SSL connections (Key exchanges) per second without session key reuse. Tender clause stands
43 Technical Specification for WAF , Page 23 , Solution Capabilities, Serial Number 6 The Application Delivery Controller shall support minimum of 30 Gbps SSL throughput and hardware compression of 30Gbps. This clause is applicable to ADC vendors and not purpose built WAFs. We as purpose built WAF do not comply to this clause and it is not related to WAF. We would request you to kindly remove this clause. Tender clause stands
44 Technical Specification for WAF , Page 24 , Solution Capabilities, Serial Number 10 Should support virtualization with its own hypervisor (NOT any third party or open source) that virtualizes the Device resources—including CPU, memory, management and configuration.The proposed device should have 8 Virtual Instances from Day 1 scalable to 20 using license upgrade. Since the ask is for a Hardware WAF, there is no reason to ask for virtualization, this clause is favoring one particular OEM and restricting other OEMs to participate. We would request you to kindly remove this clause. Tender clause stands
45 Technical Specification for WAF , Page 24 , Native and Kubernetes Integration Features, Serial Number 1 The Web Application Firewall shall have integration with REDHAT OpenShift Kubernetes Platforms and requisite controller/license/container plugin shall be provided with WAF solution from day one. Controller/Plug-in should be from same make as WAF. It should not be third party or opensource. There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
46 Technical Specification for WAF , Page 24 , Native and Kubernetes Integration Features, Serial Number 2 The Controller/Container Plugin shall support both Nodeport and ClusterIP mode of deployment and also as an Ingress service. There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
47 Technical Specification for WAF , Page 24 , Native and Kubernetes Integration Features, Serial Number 3 The Controller/Container Plugin shall support Application Delivery Controller orchestration to dynamically create and manage WAF objects. There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
48 Technical Specification for WAF , Page 24 , Native and Kubernetes Integration Features, Serial Number 4 The Controller/Container Plugin shall support PER NAMESPACE operations with the capability to run Ingress service plugins on a PER NAMESPACE basis There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
49 Technical Specification for WAF , Page 24 , Native and Kubernetes Integration Features, Serial Number 5 The Web Application Firewall shall be capable to forward traffic to container cluster via NodePort and ClusterIP. There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
50 Technical Specification for WAF , Page 24 , Native and Kubernetes Integration Features, Serial Number 6 The Controller/Container Plugin shall support the configuration of advanced services like Web application firewalls through declarative syntax. There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
51 Technical Specification for WAF , Page 25, Native and Kubernetes Integration Features, Serial Number 7 The Controller/Container Plugin shall support integration using latest Container network interface (CNI) for the container platform. There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
52 Technical Specification for WAF , Page 25,, Native and Kubernetes Integration Features, Serial Number 8 The Web Application Firewall shall support NodePort mechanism for integration with kubernetes services. There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
53 Technical Specification for WAF , Page 25 , Native and Kubernetes Integration Features, Serial Number 9 The Web Application Firewall shall support BGP for integration with kubernetes services. There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
54 Technical Specification for WAF , Page 25 , Native and Kubernetes Integration Features, Serial Number 10 The Web Application Firewall shall support overlay network like VxLAN/Geneve for integration with kubernetes services There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
55 Technical Specification for WAF , Page 25 , Native and Kubernetes Integration Features, Serial Number 11 WAF should integrates with REDHAT Openshift container orchestration environments to dynamically create L4/L7 services on WAF, and load balance network traffic across the services. Monitoring the orchstration API server, Solution should be able to modify the WAF configuration based on changes made to containerized applications. There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
56 Technical Specification for WAF , Page 25 , Native and Kubernetes Integration Features, Serial Number 12 Installation of Controller/Container Plugin should be using Operators on OpenShift Cluster and Helm charts. There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
57 Technical Specification for WAF , Page 25 , Native and Kubernetes Integration Features, Serial Number 13 Controller/Container Plugin should use open shift route resources and support route annotations. There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
58 Technical Specification for WAF , Page 25 , Native and Kubernetes Integration Features, Serial Number 14 Controller/Container Plugin should use multiple Virtual IP addresses There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
59 Technical Specification for WAF , Page 25 , Native and Kubernetes Integration Features, Serial Number 15 Controller/Container Plugin should use Custom resources extensions of the Kubernetes API. It should registers to the Kubernetes client-go using informers to retrieve Virtual Server, TLSProfile, Service, Endpoint and Node create, update, and delete events. Resources identified from such events are pushed to a Resource Queue maintained by controller. There are solutions avaialable that are dedicated for container security. We request you not to merge these clause in WAF. Within WAF, container security feature is just a checkmark feaure and wont give extensive coverage like a dedicated ccontainer security solution. As of now these are vendor specific clausse. We would request you to kindly remove this clause. REDHAT Openshift integration is critical requrement. Bidder needs to provide the solution which should be integrated with REDHAT Openshift.
60 Technical Specification for WAF , Page 25 ,Web Application Firewall Solution Functional Requirements , Serial Number 2 The Web Application Firewall Solution shall support the following Load Balancing Features This RFP is for WAF. We are a purpose built WAF however we don’t comply here. These asks are for Load Balancer and not WAF. WAF supports feuates like bloking an attack, but what is asked here is to load balance between multiple servers. Since this is not related to WAF. We would request you to kindly remove this clause. Tender clause stands
Support for 200 servers
Support load balancing algorithms
Least connection
weighted Least connection
The Web Application Firewall Solution shall have Advance security features with:
61 Technical Specification for WAF , Page 29 , Web Application Firewall Functional Requirements , Serial Number 27 The proposed solution should have server stress based L7 Behavioural DOS detection and mitigation including the ability to create real time L7 DOS signatures. You have already asked for a dedicated DDOS Solution which does Behavioral Analysis and protects against DDOS attacks. WAF works at application layer and protects against attack like SQL injection, Cross Site Scripting, HTTP Get Flood, HTTP Post Flood, Slow Loris Attacks. However L7 Behavioral protection with real time DOS Signature Creation is vendor specifc and hence We would request you to kindly remove this clause. Tender clause stands
62 Technical Specification for WAF , Page 29 , Web Application Firewall Functional Requirements , Serial Number 27 The proposed solution must support Single Sign-On functionality on the same appliance running on the same OS version from the same OEM in the future. The solution must protect against FTP, SMTP, HTTP, HTTPS, and Application layer Dos and DDOS attacks including stress based DOS and Heavy URL attacks. WAF inspects HTTP and HTTPS Traffic. For SMTP there are solutions that inspect the email body and idenify malicious request. Adding SMTP and FTP in WAF is only a checkmark feature and won't provide comprehensive security. We request you to modify the cluase to - The solution must protect against HTTP, HTTPS, and Application layer Dos and DDOS attacks including stress based DOS and Heavy URL attacks. Tender clause stands
63 Technical Specification for WAF , Page 30 , Web Application Firewall Functional Requirements , Serial Number 31 System should support inbuilt ability or integration with any 3rd party solution to encrypt the user credentials in real time at the browser level (data at rest) before the traffic hits the network so as to protect the credentials especially password, Aadhar number or any other sensitive parameter to protect from cyber actors, key loggers and credential stealing malware residing in the end user’s browsers. Necessary logs to be generated for audit and compliance. Any WAF is suppoed to protect the Server and inspect the request that is sent to the server. However this clause is directed towards an end users browser. It is not a WAF feature to check the browser of every end user. This is feature is not at all realted to WAF. This should be done by End Point Solutions not by WAF Solution. We would request you to kindly remove this clause as this vendor specific clause. Tender clause stands
64 Technical Specification for WAF , Page 30 , Web Application Firewall Functional Requirements , Serial Number 33 The solution should provide OWASP Compliance Dashboard which provides holistic and interactive interface that clearly measures app's compliancy against the OWASP Application Security Top 10 and also provide suggestions/shortcuts to address the compliances and configure policies for it. While we do protect against all kinds of OWASP attacks, the word " OWASP Compliance Dashboard" is used by only One Vendor. We do have dashboards that can show the attacks that have been blocked but it is not called "OWASP Compliance Dashboard ".The way this clause is written is vendor specific. We would request you to kindly modify this caluse as below:- The solution should provide Dashboard which provides holistic and interactive interface that clearly shows app's protection against the OWASP Application Security Top 10. Tender clause stands
65 Technical Specification for WAF , Page 30 , Web Application Firewall Functional Requirements , Serial Number 35 System should support inbuilt ability or integration with any 3rd party solution to encrypt the user credentials in real time at the browser level (data at rest) before the traffic hits the network so as to protect the credentials especially password, Aadhar number or any other sensitive parameter to protect from cyber actors, key loggers and credential stealing malware residing in the end user’s browsers. Necessary logs to be generated for audit and compliance. Any WAF is suppoed to protect the Server and inspect the request that is sent to the server. However this clause is directed towards an end users browser. It is not a WAF feature to check the browser of every end user. This is feature is not at all realted to WAF. This should be done by End Point Solutions not by the WAF SOlution. We would request you to kindly remove this clause as this vendor specific clause. Tender clause stands
66 Technical Specification for WAF , Page 30 , Web Application Firewall Functional Requirements , Serial Number 37 WAF should provide ability to enforce a given user to follow a sequences of pages while accessing An attacker may target any page of the Website. The WAF should inspect all the pages whether or not a sequence is followed or not. Also it is not feasible to define the sequence for every page of every application. This ask is not related to WAF and is vendor specific. We would request you to kindly remove this clause. Tender clause stands
67 Technical Specification for WAF , Page 31 , Management and Reporting , Serial Number 5 WAF should provide the application visibility and reporting with the below metrics and entity for each application: Most of these reports are related to Load Balancer and ADC and not related to WAF. We request you to remove this clause. The WAF dashboard is more realted showing detials about the attack and why WAF blocked the request. It doesn’t look into the performance metrics. That is generally captured by tools like APM as those can provide granular details about performance rahter that focussing on security. The clause in its current form is vendor specific. We would request you to kindly modify the clause as below:- WAF should provide the application visibility and reporting with the below metrics and entity for each application: Tender clause stands
• Client IP addresses/subnets as well as geographical regions Yes we do identify Client IP and Geo Location for any malicious request. • Client IP addresses/subnets as well as geographical regions Tender clause stands
• Total Transactions as well as Average and Max Transactions/sec We do have this as a real time dashboard. • Total Transactions as well as Average and Max Transactions/sec Tender clause stands
• Most commonly requested URLs No Tender clause stands
• Server Latency and Page Load times No Tender clause stands
• Virtual Server and Pool server performance No Tender clause stands
• Page Load Time No Tender clause stands
• Response code Yes, for every malicious request we send 403. • Response code Tender clause stands
• OS and Browser Yes, we have this for malicious request. • OS and Browser Tender clause stands
• URL details Yes, we have this for malicious request. • URL details Tender clause stands
68 Technical Specification for WAF , Page 32 , Users Access for Management , Serial Number 7 The Web Application Firewall shall generate alarms w.r.t. health status of Server/s, security alarms for TCP SYN attacks, DoS attacks, etc. These alarms are related to Load Balancer and ADC and DDOS solutions. and not related to WAF. We have alarms for OWASP Attakcs like SQL Injectionm Cross Site scripting etc. Since this is not realted to WAF. We would request you to kindly remove this clause. Tender clause stands
69 Technical Specification for WAF , Page 32 , Users Access for Management , Serial Number 8 The Web Application Firewall shall provide comprehensive reports (both real-time as well as Historical for at least 03 months) that can be customized as per requirement. Following are a few examples of the reports: Most of these reports are related to Load Balancer and ADC and not related to WAF. We request you to remove this clause. The WAF dashboard is more realted showing detials about the attack and why WAF blocked the request. It doesn’t look into the performance metrics. That is generally captured by tools like APM as those can provide granular details about performance rahter that focussing on security. The clause in its current form is vendor specific. We would request you to kindly modify the clause as below:- The Web Application Firewall shall provide comprehensive reports (both real-time as well as Historical for at least 03 months) that can be customized as per requirement. Following are a few examples of the reports: Tender clause stands
70 Client side concurrent TCP connections per virtual server/application/URL. No , ADC Feature Tender clause stands
71 Client side new TCP connections per second per virtual server/application/URL. No , ADC Feature Tender clause stands
72 Server side concurrent TCP connections per server. No , ADC Feature Tender clause stands
73 Server side new TCP connections per second per server. No , ADC Feature Tender clause stands
74 Total Input as well as Output “Bytes per second” OR “Bits per second” per No , ADC Feature Tender clause stands
75 vserver/application/URL in order to have the usage of Internet Bandwidth. No , ADC Feature Tender clause stands
76 Total Input as well as Output “Bytes per second” OR “Bits per second” between the equipment and a particular Server. No , ADC Feature Tender clause stands
77 Server Uptime and downtime reports. No , ADC Feature Tender clause stands
78 CPU and Memory utilization of the equipment. Yes CPU and Memory utilization of the equipment. Tender clause stands
79 Dozens of predefined Web application security reports such as session hijacking, Yes Dozens of predefined Web application security reports such as session hijacking, Tender clause stands
80 non-valid XML structure, CCN leakage Yes non-valid XML structure, CCN leakage Tender clause stands
81 Reports detailing learned application resources Yes Reports detailing learned application resources Tender clause stands
82 Audit and access reports Yes Audit and access reports Tender clause stands
83 PCI compliance reports allow to drill down to relevant PCI DSS section providing system compliance information No, Vendor Specific Tender clause stands
84 Top attackers, Top targeted applications, Top Intrusions/Attacks Yes Top attackers, Top targeted applications, Top Intrusions/Attacks Tender clause stands
85 Reports based on Anonymous Proxies, TOR IP addresses & Malicious IP addresses. Yes Reports based on Anonymous Proxies, TOR IP addresses & Malicious IP addresses. Tender clause stands
86 The Web Application Firewall shall conform to UL 60950 or IEC 60950 or CSA 60950 or EN 60950 or equivalent Indian Standards like IS-13252 (Part 1):2010 for Safety requirements of Information Technology Equipment. These are vendor specific ceritficates. We request you to kinldy add few other similar Certifications to enable us to participate. We would request you to kindly modify the clause as below:- The Web Application Firewall shall conform to CE or BIS or UL 60950 or IEC 60950 or CSA 60950 or EN 60950 or equivalent Indian Standards like IS-13252 (Part 1):2010 for Safety requirements of Information Technology Equipment. Tender clause stands
87 The Web Application Firewall shall conform to EN 55022 Class A/B or CISPR22 Class A/B or CE Class A/B or FCC Class A/B or equivalent Indian Standards like IS 6873(Part 7):2012 for EMC (Electro Magnetic Compatibility) requirements. These are vendor specific ceritficates. We request you to kinldy add few other similar Certifications to enable us to participate. We would request you to kindly modify the clause as below:- The Web Application Firewall shall conform to CE or BIS or EN 55022 Class A/B or CISPR22 Class A/B or CE Class A/B or FCC Class A/B or equivalent Indian Standards like IS 6873(Part 7):2012 for EMC (Electro Magnetic Compatibility) requirements. Tender clause stands
88 Hardware Details each WAF Device- The Web Application Firewall shall have at least 04 nos. 10G base-X ports complying to IEEE 802.3ae standard which is able to drive the link up to 250 Meter at speed of 10 Gbps on Multi Mode fiber. The hardware of all these ports should be complete in all respect. 10gig interface should be upgradeable to 25Gig by changing transceivers only. The Web Application Firewall shall have at least 04 nos. 10G base-X ports complying to IEEE 802.3ae standard which is able to drive the link up to 250 Meter at speed of 10 Gbps on Multi Mode fiber. The hardware of all these ports should be complete in all respect. Please remove the clause of 25G Ports as you have already asked for 40G Options in WAF. Tender clause stands
89 The Web Application Firewall shall have minimum 02 nos. 40Gig ports and at least 02 nos. 25Gig ports from day 01 The Web Application Firewall shall have minimum 02 nos. 40Gig ports and Please remove the clause of 25G Ports as you have already asked for 40G Options in WAF. Tender clause stands
90 The Web Application Firewall shall have 4 x 10G : 2 x 25G: 2 x 40G Transceivers module/SFP populated from day 01 The Web Application Firewall shall have 4 x 10G : 2 x 40G Transceivers module/SFP populated from day 01 Please remove the clause of 25G Ports as you have already asked for 40G Options in WAF. Tender clause stands
91 The Web Application Firewall Solution shall be able to learn the Web Application Structure & elements to address the difficulty of configuring the positive security model. Please delete this point Tender clause stands
92 The Web Application Firewall Solution in learning mode shall be able to recognize application changes while simultaneously protecting Web applications and learned values shall be used as the configuration for input checking in the positive security model. Please delete this point Tender clause stands
93 WAF / WAF’s Operating System should be tested and certified for EAL 2 / NDPP (Network Device Protection Profile)/NDcPP (Network Device collaborative Protection Profile) or above under Common Criteria Program for security related functions or under Indian Common Criteria Certification Scheme (IC3S) by STQC, MeitY, Govt. of India. Please delete this point Tender clause stands
94 The WAF solution should be in the Gartner's Magic Quadrant of Latest published Gartner Report “Web Application and API Protection” Please delete this point Tender clause stands
95 System should support horizontal and vertical port scanning behavioural protection or System should protect against port scanning of vulnerable services on a system, and mitigate DoS attacks, Different OEM has different terminology for similar functions. So, We would like to Request the Honourable tendering committee to amend the clause System should support horizontal and vertical port scanning behavioural protection or System should protect against port scanning of vulnerable services on a system, and mitigate DoS attacks. Please delete this point Tender clause stands
96 Clause can be read as "Positive Security Model should have advanced behavior- analysis/challenge response/http authentication technologies to separate malicious threats from Please delete this point Tender clause stands
97 This clause can be read as "System should support DNS Challenge/DNS Source Verification and DNS Rate Limit" Please delete this point Tender clause stands
98 "System should support HTTP Challenge Response authentication without Scripts/client authentication" Please delete this point Tender clause stands
99 Sufficient number of signature is very important to address known attacks. The asked deployment mode is minimum requirement. Clause Amended. Clause can be read as "System should support In- Line/Bridge, SPAN Port/TAP Mode, Out-of-Path deployment modes from day 1. The proposed device should also support 5000+ inbuilt Please delete this point Tender clause stands
100 WAF / WAF’s Operating System should be tested and certified for EAL 2 / NDPP (Network Device Protection Profile)/NDcPP (Network Device collaborative Protection Profile) or above under Common Criteria Program for security related functions or under Indian Common Criteria Certification Scheme (IC3S) by STQC, MeitY, Govt. of India. WAF / WAF’s Operating System should be tested and certified for EAL 2 / NDPP (Network Device Protection Profile)/NDcPP (Network Device collaborative Protection Profile) or above under Common Criteria Program for security related functions or Please modify this point Tender clause stands
Tap a document below to read it instantly. You can also download everything as a ZIP if you prefer.
listing-row.html
html • 0.00 MB
77c13bde4bc54a5d9a63720576d52b6f.pdf
pdf • 0.68 MB
ee1c95b1add44334bc7d0b2f2098e0c6.xlsx
xlsx • 0.04 MB
COR2587b0d443544191ae9e19c7d4b6dbf8.pdf
pdf • 0.45 MB
Download all tender documents and submit your bid
Disclaimer: TenderKart has made every reasonable effort to ensure that the information on this page is accurate and authentic, however it cannot be held liable for any third-party claims or losses or any damages. TenderKart makes no warranty, expressed or implied, as to the results obtained from the use of this information. If you notice any error or omission, please let us know at .