Conclusion - IBM Tivoli and Cisco User Manual

Action
Define or create HTML
pages for assistance with
remediation process.
Configure remediation
workflows.

4.4 Conclusion

Armando Banking Brothers Corporation (ABBC) is a company with a long history
of leading-edge technology adoption. ABBC is well aware of the rising threats of
computer viruses, worms, and the exploitation of known system vulnerabilities for
which preventive measures exist. ABBC previously installed several IBM Tivoli
security products in order to provide secure, scalable identity and access
management of their IT infrastructure. More recently, in the face of growing
concerns over threats, compliance-related risk, and government regulations,
ABBC installed the IBM Security Compliance Manager product and uses it to
proactively monitor compliance of their servers.
As the next major undertaking, ABBC is extending the Security Compliance
Manager coverage to include the workstation systems of their internal and mobile
workforce. The deployment of the Security Compliance Manager client to the
ABBC workstations, through integration with Cisco Systems componentry,
enables ABBC to deploy a Network Admission Control system based on posture
compliance status.
ABBC intends to build the solution out of three major parts. The first part includes
the deployment of the Security Compliance infrastructure and establishment of
baseline posture policies. The second part covers the deployment and
configuration of the network components to limit the network access for the
noncompliant workstations. Finally, the third part extends the solution to include
automatic remediation reusing the already existing Software Distribution
software.
Notes
Maps the posture policy to
meaningful information to
inform the user why they
have been marked
noncompliant, as well as
what steps they have to
take to remediate.
Links the Security
Compliance Manager
policy to the remediation
actions.
Chapter 4. Armando Banking Brothers Corporation
Reference
8.3, "Creating
remediation instructions
for the users" on
page 397
8.4, "Building the
remediation workflows"
on page 417
91