公司规模
Mid-size Company
地区
- Europe
- America
国家
- United Kingdom
- Ukraine
- United States
产品
- Web Security
- Cloud Security (CASB)
技术栈
- Cloud-based security
实施规模
- Enterprise-wide Deployment
技术
- 网络安全和隐私 - 云安全
适用行业
- 药品
适用功能
- 产品研发
用例
- 网络安全
服务
- 云规划/设计/实施服务
关于客户
Veramed 是一家从事制药行业的合同研究组织。该公司为进行临床试验的客户提供统计分析。在过去十年中,Veramed 已发展到拥有 275 名员工,在英国、乌克兰、美国和其他几个地方设有办事处。Veramed 成立于云计算热潮之初,从未拥有过内部服务器或传统的边界安全。该公司需要一种基于云的解决方案来保护其员工免受恶意软件和不当网站的侵害,同时还支持遵守国际安全标准。
挑战
Veramed 是一家制药行业的合同研究机构,在纯云业务环境中,它面临着监控和保护员工的挑战。该公司从未拥有过本地服务器或传统的边界安全措施,因此很难保护员工免受恶意软件和不当网站的侵害。随着公司的不断发展,它需要规范其安全性,以向客户保证其运营符合严格的标准,例如 ISO 271001。Veramed 需要通过加强对员工行为的认识来提高其监控能力,使其能够解决任何问题并为用户提供有关安全、可靠 IT 使用的教育。
解决方案
为了满足安全需求,Veramed 寻求新的网络安全提供商,并通过经销商 Qual 将其介绍给 Censornet。Censornet 提供了一种解决方案,可以将其云安全 (CASB) 融入其网络安全产品中,从而有效地将监控和安全功能扩展到关键业务应用程序。实施过程非常简单,并根据 Veramed 的需求量身定制。该部署于 2022 年中期向近 300 名用户上线。借助 Censornet,Veramed 现在可以了解其员工正在使用哪些云解决方案以及原因,发现员工是否正在使用未经授权、可能存在危险的应用程序并采取适当的措施。
运营影响
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.