TCO-aware provisioning of information security infrastructure


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News TCO-aware provisioning of information security infrastructure
# 1  
Old 11-26-2008
TCO-aware provisioning of information security infrastructure

HPL-2008-195 TCO-aware provisioning of information security infrastructure - Robinson, Philip; Stephenson, Bryan
Keyword(s): TCO automated security infrastructure provisioning
Abstract: As IT infrastructure proliferates, higher-level security controls must become interpretable and enforceable by machines, largely without human intervention. We establish a single provisioning model and process for addressing security and the Total Cost of Ownership (TCO). The innovation is the combi ...
Full Report

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Cybersecurity

Information Security Certification ??

Hi All I am not sure this is the right place to ask this question. I am from India ( Mumbai ) .I am in IT industry ( as Application developer / System support ) for nearly 4 years i dont have any direct security related work experience but i did work on cryptography & Access control in 2... (4 Replies)
Discussion started by: zedex
4 Replies
Login or Register to Ask a Question
THIN_CHECK(8)						      System Manager's Manual						     THIN_CHECK(8)

NAME
thin_check - repair thin provisioning metadata on device or file SYNOPSIS
thin_check [options] {device|file} DESCRIPTION
thin_check checks thin provisioning metadata created by the device-mapper thin provisioning target on a device or file. OPTIONS
-q, --quiet Suppress output messages, return only exit code. -h, --help Print help and exit. -V, --version Output version information and exit. --super-block-only Only check the superblock is present. --skip-mappings Skip checking of the block mappings which make up the bulk of the metadata. --ignore-non-fatal-errors thin_check will only return a non-zero exit code if it finds a fatal error. An example of a on fatal error is an incorrect data block reference count causing a block to be considered allocated when it in fact isn't. Ignoring errors for a long time is not advised, you really should be using thin_repair to fix them. EXAMPLE
Analyses and repairs thin provisioning metadata on logical volume /dev/vg/metadata: thin_check /dev/vg/metadata The device may not be actively used by the target when running. DIAGNOSTICS
thin_check returns an exit code of 0 for success or 1 for error. SEE ALSO
thin_dump(8) thin_repair(8) thin_restore(8) thin_rmap(8) thin_metadata_size(8) AUTHOR
Joe Thornber <ejt@redhat.com> Heinz Mauelshagen <HeinzM@RedHat.com> Red Hat, Inc. Thin Provisioning Tools THIN_CHECK(8)