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
SG_GET_LBA_STATUS(8)						     SG3_UTILS						      SG_GET_LBA_STATUS(8)

NAME
sg_get_lba_status - send SCSI GET LBA STATUS command SYNOPSIS
sg_get_lba_status [--brief] [--help] [--hex] [--lba=LBA] [--maxlen=LEN] [--raw] [--verbose] [--version] DEVICE DESCRIPTION
Send the SCSI GET LBA STATUS command to the DEVICE and outputs the response. This command was introduced in (draft) SBC-3 revision 20 and devices that support logical block provisioning should support this command. The default action is to decode the response into one LBA status descriptor per line output to stdout. The descriptor LBA is output in hex (prefixed by '0x') and the number of blocks is output in decimal followed by the provisioning status in decimal. The provisioning status can be in the range 0 to 15 of which only 0 (mapped), 1 (unmapped) and 2 (anchored) are used currently. The amount of output can be reduced by the --brief option. OPTIONS
Arguments to long options are mandatory for short options as well. -b, --brief when use once then one LBA status descriptor per line is output to stdout. Each line has this format: "0x<descriptor_LBA> 0x<blocks> <provisioning_status>". So the descriptor LBA and blocks are output in hex and the provisioning status in decimal. When used twice (e.g. '-bb' or '--brief --brief') the provisioning status of the given LBA (or LBA 0 if the --lba option is not given) is output to stdout. A check is made that the given LBA lies on the range of the first returned LBA status descriptor (as it should according to SBC-3 revision 20) and warnings are sent to stderr if it doesn't. -h, --help output the usage message then exit. -H, --hex output response to this command in ASCII hex. -l, --lba=LBA where LBA is the starting Logical Block Address (LBA) to check the provisioning status for. Note that the DEVICE chooses how many following blocks that it will return provisioning status for. -m, --maxlen=LEN where LEN is the (maximum) response length in bytes. It is placed in the cdb's "allocation length" field. If not given then 24 is used. 24 is enough space for the response header and one LBA status descriptor. LEN should be 8 plus a multiple of 16 (e.g. 24, 40, and 56 are suitable). -r, --raw output response in binary (to stdout). -v, --verbose increase the level of verbosity, (i.e. debug output). Additional output caused by this option is sent to stderr. -V, --version print the version string and then exit. NOTES
In SBC-3 revision 25 the calculation associated with the Parameter Data Length field in the response was modified. Prior to that the byte offset was 8 and in revision 25 it was changed to 4. For a discussion of logical block provisioning see section 4.7 of sbc3r29.pdf at http://www.t10.org (or the corresponding section of a later draft). EXIT STATUS
The exit status of sg_get_lba_status is 0 when it is successful. Otherwise see the sg3_utils(8) man page. AUTHORS
Written by Douglas Gilbert. REPORTING BUGS
Report bugs to <dgilbert at interlog dot com>. COPYRIGHT
Copyright (C) 2009-2012 Douglas Gilbert This software is distributed under a FreeBSD license. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR- POSE. SEE ALSO
sg_write_same(8), sg_unmap(8) sg3_utils-1.35 November 2012 SG_GET_LBA_STATUS(8)