Delivering business value with a secure enterprise

Latest Articles

Secure DevOps | April 13, 2021
Choosing a Software Configuration Management System Part 2
This is the second in a series of blog posts exploring characteristics of development projects to consider when choosing a Software Configuration Management system. Including Build and Release Traceability, Change Traceability, Project Lifecycle Traceability and Distributed Teams.
Secure DevOps | April 7, 2021
Choosing a Software Configuration Management System
This is the first in a series of blog posts exploring characteristics of development projects to consider when choosing a Software Configuration Management system. A Software Configuration Management (SCM) system is an essential part of almost any effective software development project. It can provide solutions to different challenges faced by the many roles in a development team. These roles include software engineers/developers, project leaders, release engineers, process engineers, engineering managers, and even engineering executives.    Although all software development projects share many common characteristics, the differences between the projects often dictate the degree of sophistication needed in the underlying development tools. Characteristics that drive the need for a highly sophisticated SCM system can include projects with numerous developers, project teams spread across many different physical locations, projects dealing with a huge software system, projects needing tightly controlled security, projects with complex process automation and enforcement requirements, and projects subject to critical regulatory requirements. If you think of increasing sophistication represented by a series of layers, or strata, each of the aforementioned characteristics can push a project into higher strata. Many SCM systems can satisfy the needs in the lower strata.  Few are powerful enough and flexible enough to handle the higher strata. HCL VersionVault is without doubt, the most flexible SCM system in the world. It supports a wide variety of deployment models for local or globally distributed teams; provides a simple process model as well a highly customizable option; includes a wide variety of powerful graphical user interfaces (GUIs) in addition to a comprehensive command line interface (CLI); provides unique build tools that generate a detailed audit trail and enable high-speed parallel builds; and integrates with a wide variety of other tools including Eclipse, Microsoft Visual Studio, Cadence Virtuoso, workflow and lifecycle management/engineering tools, etc. POSSIBLE PROJECT NEEDS TO CONSIDER An SCM...
Secure DevOps | December 7, 2020
VersionVault brings SCM/DM capabilities to EDA World – with Cadence Virtuoso Integration
HCL VersionVault is a secure enterprise solution for version control and configuration management. With HCL VersionVault  - Cadence Virtuoso Integration, VersionVault  brings its enterprise configuration management capabilities to analog and mixed signal designers. This integration enables designers to take advantage of core capabilities of VersionVault, without leaving their familiar design environment. This integration allows custom chip designers to complete VersionVault actions from within Cadence Virtuoso.  Salient Features: VersionVault Cadence integration offers advanced sets of capabilities which makes it a right fit for IC designers. Figure 1: Integration Capabilities  Instant Workspace Creation With Dynamic views, irrespective of size of design libraries (running into GBs), designers can create their workspaces based on a desired configuration instantaneously. No client side downloading of content is needed.  Rich Graphical & Command-line support Integration supports all prominent design management use cases from Cadence Virtuoso's graphical interfaces i.e. Library Manager, Cell View Editors. Integration does provide a dedicated command-line interface as well for all major design management operations.  Library Manager: Figure 2: DM Operations via Context Menu's in LM Cell View Editors: Figure 3: DM Operations via CVE Command Line Figure 4: Command Line Interface Interactive Graphical Schematic Diff Schematic diff tool enables designers to graphically browse-through and review changes made across versions of the same schematic design. This tool will provide means to the designers to navigate through any addition, deletion or modification which may have taken place between the schematic versions being compared. During the navigation, the tool will also highlight the deltas on the schematic editor in case they happen to be part of any visible design component.  Figure 5: Graphical Schematic Diff Hierarchical Design Management The Hierarchy Manager GUI provides a powerful mechanism for examining and traversing a design hierarchy. On the specification tab, designer can specify various descent controls supported with advanced...
Secure DevOps | October 19, 2020
Stepping up the productivity ladder with HCL VersionVault
This blog talks about HCL VersionVault helps the organization to step up the productivity ladder, leading to a better customer experience.
Secure DevOps | September 29, 2020
More Flexibility for VOB Element Protection
WHAT'S THE PROBLEM?     HCL VersionVault administrators often need to set up access controls on VOB elements to meet their companies' information security policy.  Operating system groups are a popular way to manage protections: users are assigned to groups, and those groups are used for element access checks.    This works nicely when groups are used for VOB element access control lists (ACLs), introduced in VersionVault 8.0.1, or for UNIX-style mode bit checks based on the VOB element's group ownership.  However, it only works as long as a single user only needs 16 or fewer groups to access all authorized elements.  VOB element ACLs can reduce the need for a user to be a member of multiple groups:  instead of having one user with multiple groups accessing elements each with a single group, you configure the ACL to protect elements to be accessible by multiple groups and each user only needs one (or a few) group(s) to access the elements.    For example, a shared component "S" would allow access to the groups representing the teams that consume that component ("A" and "B") and to the team that maintains the component ("S").  Then the developers of components A and B only need membership in the respective team-group (A or B), and the developers of the shared component only need membership  in group S.    But some administrators had extra burdens managing their group membership this way: their organization's security policy was built around separate groups for each component, with users assigned membership in the groups needed for all components their project used. ACLs could solve the problem technically but the management of ACLs to allow multiple groups per element had a higher administrative overhead than using a single group per element.    In the above example, developers for component A need membership in group...
Uncategorized | September 14, 2020
VersionVault around the DevOps Clock
HCL VersionVault is a great tool, but there is not a magic tool to do everything we need. This is also true in DevOps. Thus, HCL VersionVault read blog for more details.

Upcoming Event

No upcoming events