World’s Steel Manufacturing Leader Adopts Fasoo Enterprise DRM as its Global Standard Data Security Platform
Since its foundation in 1968, the leading steel manufacturing company has been dedicated to manufacturing of advanced and finest steel products and the related technologies and services that meet the contemporary industry and market needs. The multinational conglomerate has 32,207 employees at 26 affiliates in more than 20 countries worldwide. The company recorded 38.2 million tons of crude steel production in 2013 and marked the world’s largest steel manufacturing company by market value in 2010. They ranked within the top 200 in Fortune Global 500 for three consecutive years (2011~2013). They currently operate two integrated steel mills in Asia, and operates a joint venture with U.S. Steel, in Pittsburg, California, United States.
With 26 affiliates in over 20 countries, some of them have implemented Fasoo Enterprise DRM solutions independently. The Group faced an increased need for data security and data collaboration among its affiliates, due largely to ever-increasing business needs involving data collaboration. The Group made a decision to implement a new group-wide data security system and integrate the existing, independent enterprise DRM systems into it, so that all affiliates can protect their documents persistently and safely share documents each other as needed.
According to a directive from the steering board that specifies general requirements for the group’s standard data security platform, it is a must to enforce affiliate-exclusive security policies while allowing data share among affiliates for selective documents. In addition, exception management was also a big hassle.
The concept of the group’s standard data security platform assumed a central policy server that can cover thousands of client PCs distributed in many regions. This means that the software updates and patches as well as policy changes need to be applied to all client PCs concurrently and stably, irrespective of the time differences and variations in the network condition.
To persistently protect all documents in all affiliates, Fasoo Enterprise DRM was deployed. When documents are created, they are automatically encrypted with a default document class. This default document class enforces an affiliate-exclusive security policy, so the applicable documents are only shared within the affiliate, not among affiliates.
A custom document class was also provided to enforce a uniform, group-wide security policy, and thus to safely facilitate data collaboration among affiliates. Documents with custom document class can be shared to and accessed by all affiliates. The custom document class is enforced to selective documents only when approved by the line of business manager, and the existing enterprise portal workflows were leveraged for this request-and-approval process.
To handle inevitable exceptions, Fasoo added provisional permission request & approval process to the enterprise portal. Through the approval process, Fasoo Enterprise DRM administrators of each affiliate grant provisional document permissions to users on a request-and-approval basis. All user and admin activities pertaining to provisional permissions are traced real time for audit purpose.
To dynamically and concurrently distribute patches and software updates, Fasoo deployed an update server on Amazon Web Service (AWS) cloud. With the primary policy server running in Asia, they can ensure software updates and patches are applied to all client PCs of all affiliates concurrently.
Through deploying Fasoo Enterprise DRM to all affiliates, they can ensure compliance with its internal directive for persistent protection of internal communication documents while making it possible for affiliates to share and collaborate documents on demand without compromising the security of internal documents. Safe document exchange among affiliates significantly reduced the risk of data loss, while facilitating data collaboration and productivity. The ROI of the enterprise portal is increased, by the integration of workflows data class conversion and provisional permission.