技术
- 网络安全和隐私 - 端点安全
- 网络与连接 - 网关
适用行业
- 国家安全与国防
- 药品
用例
- 供应链可见性(SCV)
- 篡改检测
服务
- 网络安全服务
- 系统集成
关于客户
TopRx 是全国领先的仿制药、非处方药、维生素和家庭保健产品供应商。该公司将 90 家制造商的这些产品分销到美国 50 个州的 7,000 多家药店。作为记录授权经销商 (ADR),该公司为其客户和制造合作伙伴提供定制服务和出色的支持。 TopRx 总部位于田纳西州孟菲斯,在美国各地设有销售办事处和远程员工。该公司的首要任务是确保不间断运营,而强大的安全态势是实现这一目标不可或缺的一部分。
挑战
TopRx 是一家全国领先的仿制药、非处方药、维生素和家庭保健产品供应商,在向远程端点提供强大的保护方面面临着重大挑战。该公司需要通过更好地了解威胁来增强其安全态势并简化端点安全管理。 COVID-19 大流行迫使员工在家工作,TopRx 需要将保护范围扩大到他们的系统。该公司的首要任务是确保不间断运营,而强大的安全态势是实现这一目标不可或缺的一部分。在疫情爆发之前,该公司的大多数用户和端点都位于本地,并由 Check Point 下一代安全网关提供保护。我们面临的挑战是找到一种解决方案,能够为所有端点(无论是在企业网络内还是企业网络外)提供持续保护,并主动检测、识别和修复威胁。
解决方案
TopRx 选择 Check Point Harmony Endpoint 作为其挑战的解决方案。 Harmony Endpoint 是一个完整的端点安全解决方案,旨在保护远程员工免受网络威胁。它可以防止勒索软件、网络钓鱼和偷渡式恶意软件影响端点,同时通过自主检测和响应最大限度地减少违规影响。 TopRx 团队报告称,部署快速且简单。他们打包了 Harmony Endpoint 功能,以实施其台式机系统、笔记本电脑和服务器所需的特定保护。使用内置部署策略,团队在大约两天内保护了所有端点。 Harmony Endpoint 强大的反勒索软件功能可提供全面的攻击遏制和修复,以快速恢复任何受感染的系统。反勒索软件功能会在用户工作时创建小型文件备份。如果该软件检测到勒索软件开始加密文件,它会终止加密过程并立即恢复可能丢失的文件。
运营影响
数量效益
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.