公司规模
Large Corporate
国家
- Worldwide
产品
- Bitglass Breach Discovery Engine
技术栈
- Firewall
- TOR nodes
- DNS server
实施规模
- Enterprise-wide Deployment
技术
- 网络安全和隐私 - 网络安全
适用行业
- 药品
适用功能
- 商业运营
用例
- 网络安全
服务
- 网络安全服务
关于客户
本案例研究中的客户是一家拥有 20,000 多名员工的全球制药巨头。该公司是制药行业的重要参与者,生产各种药品和医疗产品。该公司拥有强大的基础设施,并投资了领先供应商的高端防火墙技术。然而,尽管采取了这些措施,该公司仍面临着重大的安全挑战。新任 CISO 热衷于评估现有的安全基础设施,以识别任何潜在的漏洞和风险。该公司规模庞大,业务遍布全球,使其成为网络威胁的潜在目标,因此,采取强大而有效的安全措施至关重要。
挑战
这家拥有 20,000 多名员工的全球制药巨头在安全态势方面面临着重大挑战。新任首席信息安全官希望评估现有的安全基础设施。尽管该公司拥有来自领先供应商的高端防火墙,但风险仍然存在。Bitglass 漏洞发现引擎在网络上发现了几个高风险的影子 IT 云应用程序。一个未经批准的云应用程序尤其令人担忧,因为员工使用它来同步他们的联系人列表和日历。然而,最令人震惊的发现是发现了三大风险:一个与 TOR 节点联系的内部 IP、十二个与托管钓鱼网站的假 DNS 服务器联系的内部节点,以及三十多个与防火墙外已确认的恶意软件主机联系的内部 IP。
解决方案
该公司安全挑战的解决方案是 Bitglass 漏洞发现引擎。首席信息安全官将四天的防火墙日志上传到引擎,然后引擎分析数据以识别潜在风险和漏洞。引擎识别出网络上的几个高风险影子 IT 云应用程序,其中包括员工用来同步联系人列表和日历的应用程序。更令人担忧的是引擎识别出的三大风险:与 TOR 节点联系的内部 IP、与托管钓鱼网站的假 DNS 服务器联系的十二个内部节点,以及与防火墙外已确认的恶意软件主机联系的三十多个内部 IP。引擎提供的漏洞发现报告按风险顺序列出了受感染的 IP 地址,以便快速调查、隔离和补救。
运营影响
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
相关案例.
Case Study
Case Study: Pfizer
Pfizer’s high-performance computing software and systems for worldwide research and development support large-scale data analysis, research projects, clinical analytics, and modeling. Pfizer’s computing services are used across the spectrum of research and development efforts, from the deep biological understanding of disease to the design of safe, efficacious therapeutic agents.
Case Study
Fusion Middleware Integration on Cloud for Pharma Major
Customer wanted a real-time, seamless, cloud based integration between the existing on premise and cloud based application using SOA technology on Oracle Fusion Middleware Platform, a Contingent Worker Solution to collect, track, manage and report information for on-boarding, maintenance and off-boarding of contingent workers using a streamlined and Integrated business process, and streamlining of integration to the back-end systems and multiple SaaS applications.
Case Study
Process Control System Support
In many automated production facilities, changes are made to SIMATIC PCS 7 projects on a daily basis, with individual processes often optimised by multiple workers due to shift changes. Documentation is key here, as this keeps workers informed about why a change was made. Furthermore, SIMATIC PCS 7 installations are generally used in locations where documentation is required for audits and certification. The ability to track changes between two software projects is not only an invaluable aid during shift changes, but also when searching for errors or optimising a PCS 7 installation. Every change made to the system is labour-intensive and time-consuming. Moreover, there is also the risk that errors may occur. If a change is saved in the project, then the old version is lost unless a backup copy was created in advance. If no backup was created, it will no longer be possible to return to the previous state if and when programming errors occur. Each backup denotes a version used by the SIMATIC PCS 7 system to operate an installation. To correctly interpret a version, information is required on WHO changed WHAT, WHERE, WHEN and WHY: - Who created the version/who is responsible for the version? - Who released the version? - What was changed in the version i.e. in which block or module of the SIMATIC PCS 7 installation were the changes made? - When was the version created? Is this the latest version or is there a more recent version? - Why were the changes made to the version? If they are part of a regular maintenance cycle, then is the aim to fix an error or to improve production processes? - Is this particular version also the version currently being used in production? The fact that SIMATIC PCS 7 projects use extremely large quantities of data complicates the situation even further, and it can take a long time to load and save information as a result. Without a sustainable strategy for operating a SIMATIC PCS 7 installation, searching for the right software version can become extremely time-consuming and the installation may run inefficiently as a result.
Case Study
ELI LILLY ADOPTS MICROMEDIA’S ALERT NOTIFICATION SYSTEM
Pharmaceutical production is subject to a strict set of enforced rules that must be adhered to and compliance to these standards is critically necessary. Due to the efforts of WIN 911’s strategic partner Micromedia, Lilly was able to adopt an alarm notification infrastructure that integrated smoothly with their existing workflows and emergency hardware and protocols. These raw energy sources enable the industrial process to function: electricity, WIN-911 Software | 4020 South Industrial Drive, Suite 120 | Austin, TX 78744 USA industrial steam, iced water, air mixtures of varying quality. Refrigeration towers, boilers and wastewater are monitored by ALERT. Eli Lilly identified 15000 potential variables, but limitations compelled them to chisel the variable list down to 300. This allowed all major alarms to be covered including pressure, discharge, quantity of waste water discharged,temperature, carbon dioxide content, oxygen & sulphur content, and the water’s pH.