Supplemental Bid Bulletin No. 6

 

SUPPLY, INSTALLATION AND DELIVERY OF CYBERSECURITY MANAGEMENT SYSTEM PROJECT

 

Bid Reference No.:  BAC4G&S-2018-002

 

In relation to the issued Supplemental Bid Bulletin No. 4 (SBB4), this is to clarify that the issuance of the SBB4 was on 24 July 2018 and not 31 July 2018. In addition, below are the clarifications to be made on the answers to queries which are stated in the SBB4:

QUERY ANSWER IN SBB4 CLARIFICATIONS
Item No. 67

Endpoint count is essential when sizing endpoint security. Is the 150000 endpoints mentioned in 7.1.1.2.4.2 already the size of the final state (all 50 agencies)?

Yes. Included in this project is 15,000 endpoint agents not 150,000 which is to be distributed within 3 years.
Item No. 199

1.  How many servers?

2. How many laptops/desktops?

3. How many mobile devices?

4. How many database and what database?

5. How many and what file servers?

6. How many and what apps?

7. How many admins required per level of NoC Security (L1 to L4)?

Under Deployment Item 6

6.2 Vendor should include all necessary hardware, system storage, database, and backup for the software or system in order to ensure continuity of operations.

With the statement above for individual cybersecurity software to be delivered comes with servers, storage, backup already configured.

1. How many servers? 17

2. How many laptops/desktops?

10 workstations for Analysts (L1-L3):

– 1 work station for SOC manager

– 1 workstation for Info desk

– 1 workstation for supervisor

– 1 laptop for VAPT – 1 backup laptop

3. How many mobile devices? None.

4. How many database and what database?

– Case management system database

– Forensic database

– Database for artificial intelligence/machine learning based on the solution.

– Other required by the security software solution

5. How many and what file servers?

– Storage Server for Physical Security (CCTV)

– Storage server for access of finger vein biometric and access pad

– Other required by the security software solutions

6. How many and what apps?

7. How many admins required per level of NoC Security (L1 to L4)?

– 1 Supervisory access

– 1 for SOC manager

– 1 for SOC director

– Head of Cybersecurity Bureau

1. Minimum of 6 (depends on the solutions of the vender)

 

2. 11 workstations for Analysts, soc manager, supervisor (L1-L3):

– 2 support laptops

 

After considering the queries, clarifications, recommendations and suggestions, the BAC4G&S hereby decides to include, revise, amend, delete and/or adapt the following provisions:

ITEM NO. QUERY BAC4G&S RESPONSE
INQUIRY:

further define the “Security Operations Center (SOC)” in the Single Largest Completed Contract

 

DICT RESPONSE:

The term similar project in the SLCC (As indicated in the Bidding Documents) shall not be limited to the Security Operations Center that was established by the vendor in previous clients.

 

Similar projects shall mean similar solutions that will be offered to the end user that was deployed in previous clients. SOC shall mean same project that has threat Intelligence Platform, Case Management System, Analysis and Incident Response.

 

FOLLOW-UP CLARIFICATON:

As I understand, that the end-user defined SOC as “same project that has Threat Intelligence Platform, Case Management System, Analysis & Incident Response”.

 

I just want to clarify that since SOC is not limited to “Threat Intelligence Platform, Case Management System, Analysis & Incident Response only”, we are assuming that projects which has other SOC component (such as Firewall, IPS/IDS, Monitoring Tools, Network Attack Protection, DDoS and other security components not listed here) shall be accepted as well. Provided that the vendor will meet the requirement of: “Bidder can submit Statement of at least two (2) contracts of similar contracts of similar nature, the aggregate of which should be equivalent to at least fifty percent (50%) of the ABC, the largest of these contracts must by equivalent to at least twenty five percent (25%) of the ABC.”

It was mentioned during the Pre Bid Conference that SOC is not just limited to the establishments of the entire SOC. End-user elaborated it can include security component of the SOC such as Firewall IPS/IDS, monitoring tools, Threat Intelligence, Forensics etc.
2 42 – For the Disaster Recovery System, should it be provided by the solutions provider or DICT? – Does this assume that the DICT site will be the main site and the Public Cloud solution will be provided by the vendor? There will be no DR site that will be provided by DICT There will be no DR site that will be provided by DICT.
3 53 – b – The offsite DR will be on the cloud. Cold site only. Same capability without forensics. – When you say same capability does it mean that the off-site DR can take over the function of the main CMS without the EDR and Network ATP? Offsite DR is a cold site backup which includes the core components of the SOC, files, data, and database. This should be able to run on its normal SOC operations when it is needed.
4 53 – f – The project needs backup of both system and data to run the main systems (Redundant). Please also understand there is a separate backup of the data only. – Does it mean there will be a replication of the backup on top of the off-site DR of the Public cloud solution provided by the vendor? Yes. Since it shall be redundant, there should be a backup on-top of the the off-site DR
5 67 – Endpoint count is essential when sizing endpoint security. is the 150000 endpoints mentioned in 7.1.1.2.4.2 already the size of the final state (all 50 agencies)? – Is this a typo error? This is a typo error. It should be 15,000 endpoints.
6 71 – Only the sensor with capabilities of detecting C&C and lateral movements shall be deployed in the priority agencies. This sensor shall also do Endpoint and Network Forensics with log collection to priority agencies’’ network. – Does this translate to the EDR agents only? No more network sensors that needs to be deployed in agency site. Network forensics is part of the Agency deployment as stated in the Technical Specifications.
7 74 – The sensor that will placed in the priority agencies shall be capable of doing initial analysis to the threats found in the priority agencies’. This shall be capable of doing initial filtering of false positives and provide initial analysis to threats and incidents before the escalation to the core SOC – Does this mean that sensors equates to EDR and Endpoint agents? Yes. Please refer to the Technical Specifications for the other requirements.
8 86 – Yes. These two separate firewalls shall be able to DDOS and any excess to its capability should be able to be thrown to the cloud solution – Do you Still require WAF as part of the features for this specific requirement? It would not make sense to place this in the CMS network if there are no application to be protected. Thus, The proposed solution will only need Global Server Load Balancing and Link Load Balancing to make the services available. Solutions to be used by SOC shall be protected by firewalls. End user would to stick to the design
9 105 – The solution shall provide email/phone and SMS alerting options. – Some solutions will require a special SMS gateway for integration. Thus, an option to consider is deliver the alert via email only. Please confirm if this is a considerable option? This specification will remain as previously stated.
10 110 – c – For 7.1.1.9.16, may we know how many Servers are there from the 1,500 endpoints per agency? –  Does this mean that the acceptance for agency on-boarding will only constitute to 5000 endpoints? What if the number of agencies will not sum up to 5000? The number of servers for each agency will be disclosed with the winning vendor.
11 122 – a – The switchable privacy glass shall be placed at the conference room and SOC Manager Room. (Please see the attached floorplan for more details) – Will you allow a privacy tint instead that is also switchable using it’s electrostatic features? This specification will remain as previously stated.
12 127 – No, the Disaster Recovery Management System will be in Hybrid Form. Backup storage will be in Hybrid form and other replica of data in the SOC will be located in the cloud. Other requirements for the DR is on the Technical Specifications.  – Can we request more details as how you envision the setup for DRMS? Or to be more general, does this assume; Primary/CMS Site = DICT Site then DR Site = Public Cloud? Yes. Primary/CMS Site = DICT Site then DR Site = Public Cloud
13 137 – C – We use 2U rack mount – It was mentioned in #39 that the portable CMS should be in Laptop, can we confirm which is more appropriate? 2U or Laptop? Laptop was stated as an option in answer to the question. The portable CMS specification will remain as stated in the TOR.
14 139 – Hybrid (Both cloud and on-premise) –Can we assume that the Threat Intel Management Platform will be on-premise while the threat intel feeds will be over cloud? Yes
15 143 – b – You mentioned in number #105 that the solution shall provide email/phone and sms alerting option. Can we just reconsider an email alert option instead? This specification will remain as previously stated.
16 143 – g – No – Can we reconsider an option to place this on year 1 and years 2&3 can be in a separate budget? The subscription for the web intelligence must be 3 years.
17 143 – c – Hybrid (Cloud and On-premise) Can we assume that the operation for Web Intelligence will be over cloud while the correlation and integration to other data sources will be on-premise? Yes. Please refer to the Technical Specifications.
18 147 a –  Hybrid (Both Cloud and On-Premise). The log correlation is only for the core – Does the Hybrid entails the backup of the logs? Or a deployment model for hybrid is really the intent of this response? Logs correlation is only for the core.
19 149 a – The scope of the DR site shall include back-up and all components of the core. This is composed of two storages: on-premise and cloud. The vendor shall provide a user account for the cloudbased DR site upon delivery. – Does it mean that the on-premise storage will be situated in CMS site? The on-premise storage will be situated in the CMS site.
20 149 f- What is the interval of the snapshots? Snapshots are packaged in OVA/OVF format. Do you really need to have a real-time replication? Because this will entail additional licensing cost and this will be throughput/bandwidth intensive This will remain as stated in the Technical Specifications.
21 153 b – All ADC solutions will be based on what the vendors will provide. DICT expects the ADC to have the ability to load balance servers, web technologies and security applications. – The current CMS components does NOT need any server load balancing because it was defined in the response in #7.1.1.10.2 that there will be only 1 server for each component. Please clarify the intent for the ADC requirement. Kindly refer to the Technical Specifications for this question. ADC will be retained in the design
22 157 – The vendor will only provide 1 person per Tier and 1 Supervisor for a total of 4 personnel with consideration of the 24×7 operations. – Does this mean that there will be a DICT personnel who can also cover the gaps in-between shifts and schedules to cover 24×7? The reason is for asking is that 4 personnel may NOT be sufficient to cover 24×7 on their own considering weekends, day-offs and holidays. There will be DICT personnel who will also be manning the SOC with the 4 personnel from the vendor.
23 164 – The 99.9% availability is applicable to all components of the project – Does this constitutes that all components requires HA? This will entail additional licensing to meet the 99.9% availability Yes
24 173 – Yes, the end-user will need sensors that will deployed in the priority agencies. These sensors will also include monitoring agents as part of the technical specifications in the tor and this sensor will also do forensics (Endpoint and Network), C&C, and lateral movement detection as part of it capabilities. – Please confirm that Network is NOT part of the forensics in the Agency deployment. Otherwise, this will require Network sensors to aggregate detection and protection on the target agencies Network forensics is part of the Agency deployment as stated in the Technical Specifications.
25 178 – c. Who will be handling the installation of the network link from the main CMS site to the DR site? – Will the DR site be on a physical site or a Public cloud? DR site will be Public Cloud
26 199 – With the statement above for individual cybersecurity software to be delivered comes with servers, storage, backup already configured. 1. How many servers? 17 – What if the number of servers that we require is less than 17? Will that be considered since we’re opting for a virtualized/hyper-converged setup for some of the CMS tools? We understand that number of servers may differ based from the proposed solution. Please see amended provision.
27 222 – Yes, DICT will do the coordination to the Priority Agencies and will make sure that they will know and will comply on the requirements of the project. – What if the number of agencies installed/covered did not reach 10 or 5000 endpoints by the end of the given schedule requirements due to lack of agencies that meet the pre-requisite set by DICT? Will that affect the timeline for the project acceptance? This will not affect the timeline for project acceptance. The DICT already have an MOU/MOA with the priority agencies who are able to comply with the pre-requisites
28 229 b – Finger Vein is only for the man trap door access control. Computer login can be different specifications. – Can we use a fingerprint sensor or IR camera as a form of multi-factor authentication for all the workstations? Yes
29 243 – Yes. We only require 10 minute power of the UPS that can cater servers. – Do we also include other non-server based tools like network, perimeter, and physical security devices for the UPS quantity and capacity? Yes
30 275 e – Both – A cloud-based sandboxing solution is throughput/bandwidth intensive and takes much longer time to process a suspected file/data. Can we propose an on-premise-only solution instead? See sandbox specifications. We require to have an on premise for this.
31 Item 7.1.1.10.2 Server Rack Cabinet – Can we use less than 6 server racks and less than 12 Main rack servers for our proposed solution? Please refer to the requirements stated in the Technical Specifications.
32 Item 7.1.1.10.4 Server – Can we use other server configuration/specification like CPU, RAM, Storage, etc. that will cater to our proposed solution? Yes. Please refer to the Technical Specifications.
33 Item 7.1.1.10.5.3 Internet Load Balancer –Will the solution reside on the Main/CMS site? The cellular, 3G and 4G LTE links are not suitable for a CMS this size as a form of a back-up link. Yes. Please refer to the Technical Specifications.
34 Please also clarify the milestone of payment under pages 74 to 75 and 145 of the latest bid bulletin. Based on our computation its only 95%. Please see amended provision.
35 Disaster Recovery System

 

a. Based on pre-bid, it is clear that DR is a cold site with backup (item#42). Cloud-based backup is not part of the plan, it will be difficult to restore huge amount of date from cloud. Omit statements regarding cloud-based DR on item #53 and item #120

 

b. Active/active or active/standby datacenter, item #53. Active/active or active/standby SOC will entail additional license cost and greatly impact allocated budget.

 

c. System and platform Clustering will be used to address high-availability. This is more efficient rather than providing a secondary-standby component.

A. End-user will stick to the design. DR is a cold site with backup in the cloud. Backup on premise is also available. Kindly check requirements stated in the Technical Specifications.

 

b. End-user would like to stick to the design

 

c. End-used would like to stick to the design

36 List of hardware requirements for CMS/SOC solution. This should depend on the proposed CMS/SOC solution. Every SOC solution has its own design and architecture. This is noted.
37 SOC Supervisor can act as the consultant. Supervisor shall be part of the SOC team.
38 Clarity on all throughput requirement for Network protection tools. 20Gbps
39 Confirmation that hardware for log collectors will be supplied by DICT as stated in item #158. Vendors will provide every hardware included in the Technical Specifications. This includes the log collectors.
40 Item ##80, the response was there should be a scrubbing center that can be composed of multiple operating centers focused on volumetric attack that can accommodate up to total of 1.5Gpbs but on the new TOR it was changed to 40Gpbs, what document are we going to follow? (7.1.1.2.2.1.6.) See provision on 7.1.1.2.2.1.6
41 Item no. 276, it says that IPS on FW is acceptable but on the new TOR in reference with section 7.1.1.2.5.4., it still mentioned separate filter, filter updates and reputation database must be supported by the IPS appliance. Kindly state in the new TOR that role of IPS can be used in the Next Generation Firewall Appliance/ End user will stick 7.1.1.2.5. requirement in the Technical Specifications.
42 Item no. 247, kindly state a yes or no answer regarding our request to a front LCD panel display (section 7.1.1.2.1.1.16.) since all firewall has visual indicators? End user will stick to 7.1.1.2.1.1.16 requirement in the Technical Specifications.
43 Item no 53 Sec H – UPS configuration 2N+1. Can we propose N+1 configuration instead of 2N+1 since the redundancy was just the same and only the N capacity was increased? Yes, it can be N+1.
44 SLCC – Annex I-A: We fully understand that the said form is required by the agency to prove the capability of the bidders to support the project, however, disclosing the “Name of the Client” will infringe the rules of the contracts that we have with them, specially that the projects covers their Security/National Security. Thus, we would like to again request to allow us to leave blank the “Name of the Client” in the Annex I-A form. Similar to the documents to be attached, the “Name of the Client” will also be blackened/erased. Note though that during post-qualification, we can show the copy of the Contract with the details of the client for your assurance. Request is denied. Bidders must submit all the necessary information as indicated in Annex I-A. In addition, bidders must submit any of the following documents corresponding to listed contracts per listed Annex I-A:

a. Copy of end user’s acceptance;

b. Official receipt/s; or

c. Sales Invoice

45 Item No. 116 the WAN connection is crucial for sizing and analysis of traffic for inbound and outbound traffic This will be shown to the winning bidder
46 Item No. 278 – Can we be more specific to what thousand is it 1000^n or 100,000 of scanning per day as this is crucial for sizing. A range from 15,000 to 50,000 per day
47 Item Nos. 144 & 257 – Which is which as on 144 we are pertaining  Hybrid Manage and on 275 we are pertaining to On Prem Only can we please clarify on this? Hybrid
48 Item 268B – We would need at least an assumption to further provide a quantifiable sizing and analysis. 500 endpoint users per agency. It is part of the plan that there will be 50 agencies by 2020
49 Item no. 256 – Can we be specific what is this the actual Bandwidth for the internet as it also needed to for proper sizing and analysis. SOC internet is 200mbps. The backup is also 200mbps. Priority agencies speed is 50mbps to 100mbps
50 Section 7.1.1.10.4. Server – Some terminologies like iDRAC8 is a brand specific terminology. Can we propose a different brand with equivalent specification? Vendors are allowed to deliver any brand with equivalent specifications as long as it complies with the Technical Specifications.
51 For the Fit Out:

The TOR specifies 4×2 video wall (total of 8) but the diagram is 3×3.

This is under Item 8.4 Videowall Display (8 pcs) – page 134 / AV System Schematic Diagram – page 82

It will fit based on our diagram included in the Technical Specifications.

 

 

ORIGINAL PROVISION AMENDED PROVISION
SECTION VII. TECHNICAL SPECIFICATIONS
6.1.      For the 1st year, the solution shall cover ten (10) organizations in up to ten (10) different physical sites. These organizations are DICT, NSC, DND, DFA, PCOO, OP/PMS, DOE, DBM, DOF and NICA. 6.1 For the 1st year, the solution shall cover ten (10) organizations in up to ten (10) different physical sites.
7.1.1.2.2.3.2. The solution shall provide at least 1.5Tpbs of dedicated attack capacity 7.1.1.2.2.3.2. The solution shall provide at least 1.5Gbps application-layer DDoS attack protection
7.1.1.2.2.1.6. The solution shall have on premise protection against volumetric, state-exhaustion and application-layer DDoS attacks. 7.1.1.2.2.1.6. The solution shall have on premise protection against volumetric DDoS attacks up to 40Gbps.
7.1.1.2.3.1. The solution shall include network threat protection sensor that support Inline blocking mode or span/tap mode. 7.1.1.2.3.1. The solution shall include network threat protection sensor that span/tap mode.
7.1.1.2.3.2. Update of VM used for Dynamic Analysis can be done from the GUI without an OS upgrade. VM is built, maintained, and delivered by the vendor. This provision is deleted.
7.1.1.2.3.4. Detection appliance OS software shall automatically be updated from the Web management GUI. This provision is deleted.
7.1.1.2.3.5. VM images for malware detonation shall be upgradable from the Web Management GUI. This provision is deleted.
7.1.1.2.3.17. For the above list of applications supported in the VM’s the Vendor must have a method for pushing updates to the list of applications dynamical to the appliance without requiring a full OS or solution upgrade. This provision is deleted.
7.1.1.2.3.19. The analysis must be performed runtime in order to detect all the malware actions, even the ones that fail in the virtual environment but might be successful on a client workstation. Before and After differential comparison or VM state is not acceptable. This provision is deleted.
7.1.1.2.3.20. The solution shall be able to detect and report web exploits by using multiple versions of web browsers and plug-ins. This provision is deleted.
7.1.1.2.3.22. The solution shall be able to automatically generate a network communication profile if the malware tries to contact network resources during the analysis. This profile shall be used to determine if systems on the network are compromised. This provision is deleted.
7.1.1.2.3.23. The solution shall be able to simulate end used actions in order to force the execution of malware that rely on triggers from and end user, like a mouse click. This provision is deleted.
7.1.1.2.3.47. The solution shall have the ability to be deployed in the following modes: IN-LINE and SPAN / TAP 7.1.1.2.3.47. The solution shall have the ability to be deployed in SPAN / TAP mode
7.1.1.2.3.48. The solution shall have fail-open capability to allow all packets to pass through the sub-system in case of software, hardware or power failure when it is deployed inline. This provision is deleted.
7.1.1.2.3.50. To show the capability of the Security Vendor’s threat research or labs team, the vendor shall have a research team which has published a paper on an APT Threat Actor. The paper should not only be focused on a specific attack, but rather focused on attribution around a specific attack group. This provision is deleted.
7.1.1.2.4.1. The endpoint security solution‘s monitoring agents shall be able to be controlled on and off the corporate network for the purposes of detection, triage, and containment 7.1.1.2.4.1. The endpoint security solution‘s monitoring agents shall be able to be controlled on the corporate network for the purposes of detection
7.1.1.5.7.3. The solution shall automatically generate and send bulletin report of about the most recent cyber-attacks with recommendations to the department, priority agencies, and all government agencies that may be affected by the cyber threats. 7.1.1.5.7.3. The send bulletin report of the most recent cyber-attacks with recommendations to the department, priority agencies, and all government agencies that may be affected by the cyber threats.
7.1.1.7.16. The UPS power rating configuration shall be 2N+1 with 10 minutes runtime.  7.1.1.7.16.  The UPS power rating configuration shall be N+1 with 10 minutes runtime.
7.1.1.10.2 Server Rack Cabinet

7.1.1.10.2.1 Technical Specifications

7.1.1.10.2.1.1 Six (6) Server Rack Cabinet that will fit the twelve (12) Main Rack Servers of the CMS.

7.1.1.10.2.1.1.1 One (1) Artificial Intelligence and storage of required database, logs, files, etc

7.1.1.10.2.1.1.2 One (1) Machine Learning server and storage of required database, logs, files, etc

7.1.1.10.2.1.1.3 One (1) Case management System server and storage of required database, logs, files, etc

7.1.1.10.2.1.1.4 One (1) Forensic systems investigation and storage of required database, logs, files, etc

7.1.1.10.2.1.1.5 One (1) Systems alerts server, filtered threats feeds and storage of required database, logs, files, etc

7.1.1.10.2.1.1.6 One (1) VAPT server and storage of required database, logs, files, etc

7.1.1.10.2.1.1.7 Two (2) Sandbox servers (1 window and 1 linux) for malware extraction and investigations. Additional Virtual Machines shall be included.

7.1.1.10.2.1.1.8 One (1) Proxy Server and storage of required database, logs, files, etc

7.1.1.10.2.1.1.9 One (1) Internal server for SOC network and storage of required database, logs, files, etc

7.1.1.10.2.1.1.10 One (1) Physical Access and CCTV server and storage of required database, logs, files, etc

7.1.1.10.2.1.1.11 One (1) Monitoring Tools

 

7.1.1.10.3 Rack Servers for Backup (On premise)

7.1.1.10.3.1 Technical Specifications

7.1.1.10.3.1.1 One (1) Artificial Intelligence (Replica of the main server)

7.1.1.10.3.1.2 One (1) Machine Learning (Replica of the main server)

7.1.1.10.3.1.3 One (1) Case management System (Replica of the main server)

7.1.1.10.3.1.4 One (1) Forensic systems investigation Forensic systems investigation and storage of required database, logs, files, etc

7.1.1.10.3.1.5 One (1) Central Backup Rack Server for Multiple storage (On Premise)

7.1.1.10.3.1.5.1 Systems alerts, filtered threats

7.1.1.10.3.1.5.2 All databases

7.1.1.10.3.1.5.3 VAPT databases

7.1.1.10.3.1.5.4 Internal Server access logs

7.1.1.10.3.1.5.5 other systems backup and configuration files

7.1.1.10.3.1.5.6 Agencies logs

7.1.1.10.3.1.5.7 Internal Files

7.1.1.10.3.1.5.8 Portable CMS backup

 

7.1.1.10.4 Server

7.1.1.10.4.1 Processor

7.1.1.10.4.1.1 Latest Xeon Processors

7.1.1.10.4.1.2 Intel® Xeon® processor E7 product family

 

7.1.1.10.4.2 Memory (RAM)

7.1.1.10.4.2. 128 RAM or higher to operate the solution smoothly with free expansion slots

7.1.1.10.4.2.2 Drive Bays / Storage

7.1.1.10.4.2.2.1 256 SSD / 1 Tera SATA, with free expansion slots

 

7.1.1.10.4.3 Operating System

7.1.1.10.4.3.1 Red Hat® Enterprise Linux or any premium Linux distro

 

7.1.1.10.4.4 Chasis Compatible with Rack Cabinet

 

7.1.1.10.4.5 Security Build-in

 

7.1.1.10.4.6 Other Features

7.1.1.10.4.6.1 ECC memory

7.1.1.10.4.6.2 Hot-plug hard drives

7.1.1.10.4.6.3 Hot-plug redundant cooling

7.1.1.10.4.6.4 Hot-plug redundant power

7.1.1.10.4.6.5 Internal Dual SD Module

7.1.1.10.4.6.6 Single Device Data Correction (SDDC)

7.1.1.10.4.6.7 Spare Rank

7.1.1.10.4.6.8 Support for high availability clustering and virtualization

7.1.1.10.4.6.9 Proactive systems management alerts

7.1.1.10.4.6.10 iDRAC8 with Lifecycle Controller

 

7.1.1.10.4.7 Power Specs

7.1.1.10.4.7.1 1100W AC, 86 mm (Platinum) / 1100W DC, 86 mm / 750W AC, 86 mm (Platinum) / 750W AC, 86 mm (Titanium)

7.1.1.10.4.7.5 495W AC, 86 mm (Platinum)

 

7.1.1.10.4.8 RAID Controllers Specs

7.1.1.10.4.8.1 Internal

7.1.1.10.4.8.1.1 PERC S130 (SW RAID)

7.1.1.10.4.8.1.2 PERC H330 / PERC H730 / PERC H730P

7.1.1.10.4.8.2 External

7.1.1.10.4.8.2.1 PERC H830

7.1.1.10.4.8.2.2 External HBAs (non-RAID):12Gbps SAS HBA

7.1.1.10.4.8.2.3 Chipset: Intel C610 series chipset

 

7.1.1.10.4.9 Network Controller: 4 x 1Gb, 2 x 1Gb + 2 x 10Gb, 4 x 10Gb”

7.1.1.10.2 Server Rack Cabinet

7.1.1.10.2.1. Minimum Technical Specifications

7.1.1.10.2.1.1. 6 Server Rack Cabinet

7.1.1.10.2.1.2. The vendor shall provide a minimum of 6 servers for the main system, but this can vary depending on the proposed solution.

7.1.1.10.2.1.3 The solution shall offer a dedicated server for the sandbox.

 

7.1.1.10.3 Rack Servers for Backup (On premise)

7.1.1.10.3.1. Technical Specifications

7.1.1.10.3.1.1. The vendor shall provide backup            servers for all the servers for the main system which can easily be activated when there is an incident.

7.1.1.10.3.1.2. The solution shall assign a dedicated central server for the systems alerts, filtered threat, all databases, VAPT database, internal server access logs, other systems backup and configuration files, agencies logs, internal files, portable CMS.

 

7.1.1.10.4 Server

7.1.1.10.4.1. Processor

7.1.1.10.4.1.1. Latest  Processors (3.8GHZ)

7.1.1.10.4.1.2. Compatible Chipset

  

7.1.1.10.4.2 Memory (RAM)

7.1.1.10.4.2.1. 128 RAM or higher to operate the solution smoothly with free expansion slots

7.1.1.10.4.2.2 Drive Bays / Storage

7.1.1.10.4.2.2.1. 256 SSD / 1 Tera SATA, with free expansion slots

 

7.1.1.10.4.3 Operating System

7.1.1.10.4.3.1. Any compatible OS

 

7.1.1.10.4.4. Chasis Compatible with Rack Cabinet

 

7.1.1.10.4.5. Other Features

7.1.1.10.4.5.1. ECC memory

7.1.1.10.4.5.2. Hot-plug hard drives

7.1.1.10.4.5.3. Hot-plug redundant cooling

7.1.1.10.4.5.4. Hot-plug redundant power

7.1.1.10.4.5.5. Internal Dual SD Module

7.1.1.10.4.5.6. Chipset: Any compatible chipset

 

 

 

 

 

 

 

8.9.1.2.5. Operating Systems: any compatible OS Windows XP / Vista / 7 / 8, Linux 2.6X and above, Mac OSX 10.4 and above 8.9.1.2.5. Operating Systems: any compatible OS
8.13. SOC Desktop Package (10 units)

8.13.1. Technical Specifications

8.13.1.1.  Swift Curved Monitor – 34″ 21:9 Ultra-wide QHD (3440×1440), overclockable 100Hz , G-SYNC™

8.13.1.2. Latest Processor Intel Core i9-7920X with motherboard

8.13.1.3. At least 32GB RAM Memory

8.13.1.4. Minimum 8GIG VIDEO card dedicated

8.13.1.5. 480GB SSD + 2TB HDD

8.13.1.6. Integrated Ethernet plugs into your compatible wired network

8.13.1.7. USB 3.0 ports

8.13.1.8. Any compatible OS Windows 10

Pro latest edition

8.13.1.9. include high-end keyboard / mouse 8.13.1.10. include licensed office software Ms office 2017 up (not subscription)

8.13. SOC Desktop Package (10 units)

8.13.1.  Technical Specifications

8.13.1.1. Swift Curved Monitor – 34″ 21:9 Ultra-wide QHD (3440×1440), overclockable 100Hz , G-SYNC™

8.13.1.2. Latest Processor

8.13.1.3. At least 32GB RAM Memory

8.13.1.4. Minimum 8GIG VIDEO card dedicated

8.13.1.5. 480GB SSD + 2TB HDD

8.13.1.6. Integrated Ethernet plugs into your compatible wired network

8.13.1.7. USB 3.0 ports

8.13.1.8. Any compatible OS

8.13.1.9. include high-end keyboard / mouse

8.13.1.10. include licensed productivity software

8.14. VAPT Laptop

8.14.1. Technical Specifications

8.14.1.1. Latest Processor 7th Generation Intel® Core™ i7-7700HQ Quad Core (6MB Cache, up to 3.8 GHz)

8.14.1.2. 16 GB RAM

8.14.1.3. 256 SSD + 1 TB HDD

8.14.1.4. 15.6-inch UHD (3840 x 2160) IPS Anti-Glare LED-Backlit Display

8.14.1.5. Video Card NVIDIA® GeForce® GTX 1050 Ti with 8GB GDDR5 graphics memory

8.14. Support Laptop (2 items)

8.14.1.Technical Specification

8.14.1.1. Latest Processor 6MB Cache, up to 3.8 GHz)

8.14.1.5. 8GIG Video Card

8.14.1.6 16GB RAM

8.14.1.6. 256 SSD + 1 TB HDD

8.14.1.7. 15.6 inch laptop monitor

8.14.1.7 licensed office productivity software

 

8.15. Backup VAPT Laptop

8.15.1.   Technical Specifications

8.15.1.1. Latest Processor 7th Generation Intel® Core™ i7-7700HQ Quad Core (6MB Cache, up to 3.8 GHz)

8.15.1.2.  16 GB RAM

8.15.1.3.  256 SSD + 1 TB HDD

8.15.1.4. 15.6-inch UHD (3840 x 2160) IPS Anti-Glare LED-Backlit Display

8.15.1.5. NVIDIA® GeForce® GTX 1050 Ti with 8GB GDDR5 graphics memory

This provision is deleted.
16. Payment Terms 16. Payment Terms
Milestones Progress Milestones Progress
Upon onsite delivery of all Hardware/Software 35% Delivery

–       Onsite delivery of all Hardware and Software

30%
Upon completion of installation and configurations 10% Installation and Configuration

–       completion of installation, configurations including civil works

–       installation and Configuration of Hardware/Software to the Priority Agencies

20%
Upon completion of agreed Testing 5% Testing and Commissioning

–       Approval of Test Procedures

–       execution of VAPT to the Cybersecurity Management System’s Network

–       completion of operational stress test to the Cybersecurity Management System and Priority Agencies Network

30%
Upon execution of VAPT to the Cybersecurity Management System’s Network 5% Training and Knowledge Transfer 10%
Completion of Testing to the Cybersecurity Management System’s Network 5% Acceptance

–       submission of Agents – Built Plans, Operations & Maintenance Manuals, Warranty completion of Training Sessions

10%
Upon Installation and Configuration of Hardware/Software to the Priority Agencies 20% Total 100%
Upon completion of operational stress test to the Cybersecurity Management System and Priority Agencies Network 10%    
Upon completion of Knowledge Transfers, delivery and installations of the remaining agents and submission of As – Built Plans, Operations & Maintenance Manuals, Warranty completion of Training Sessions 5%    
Total 100%    

 

All terms, conditions and instructions to bidders specified in the Bidding Documents inconsistent with this Bid Bulletin are hereby superseded and modified accordingly.

 

Attached in this Supplemental Bid Bulletin are the following references:

  • Revised SOC Floorplan as of 30 July 2018

 

Further, please use the following forms attached in this Supplemental Bid Bulletin:

  • Revised Schedule of Requirements as of 30 July 2018
  • Revised Technical Specifications as of 30 July 2018
  • Sworn Statement as of 30 July 2018
  • Revised Statement of Completed Single Largest Contract of Similar nature within the last five (5) years from the date of submission and receipt of bids equivalent to at least fifty percent (50%) of the ABC or Statement of At Least Two (2) Contracts of Similar Nature within the last five (5) years from the date of submission and receipt of bids, the aggregate of which should be equivalent to at least fifty percent (50%) of the ABC, and the largest of these similar contracts must be equivalent to at least twenty five percent (25%) of the ABC as of 30 July 2018
  • Revised Omnibus Sworn Statements as of 30 July 2018
  • Revised Technical Bid Form as of 30 July 2018
  • Revised Financial Bid Form as of 30 July 2018
  • Revised Detailed Financial Breakdown as of 30 July 2018
  • Revised For Goods Offered From Abroad as of 30 July 2018
  • Revised For Goods Offered from Within the Philippines as of 30 July 2018

 

For information and guidance of all concerned.For a full copy of the document, click the link below:

Supplemental Bid Bulletin No. 6-SUPPLY, INSTALLATION AND DELIVERY OF CYBERSECURITY MANAGEMENT SYSTEM PROJECT

Issued this 30th day of July 2018.

 

 

(Original Signed)

JIEZL GABRIELLE G. REOTUTAR

Vice Chairperson, BAC4G&S