Best IT Documents.com Blog


Sample Excel – Network Bandwidth Delay Estimates Spreadsheet

Comments Off on Sample Excel – Network Bandwidth Delay Estimates Spreadsheet

Sample Excel – Network Speeds Spreadsheet

Comments Off on Sample Excel – Network Speeds Spreadsheet

SUDO quick Reference Guide

Usr/local/etc

Usr – OS

Usr – Alias (SUDO)

Web admin

Permissions to do

 

SUDO quick Reference Guide

sudo kill

sudo killall

sudo chown

sudo mkdir

sudo rmdir 

mysql Status

serveradmin   status mysql 

myaql Status

serveradmin   settings mysql 

Start / Stop mysql

/usr/sbin/serveradmin   start mysql

/usr/sbin/serveradmin   stop mysql           

To move a database to a new location:          

sudo /usr/sbin/serveradmin stop mysql          

sudo cp -Rp /oldpath/mysql /newpath/          

sudo /usr/sbin/serveradmin settings mysql:databaseLocation = /newpath/mysql      

sudo /usr/sbin/serveradmin start mysql                     

To change the database location:       

sudo /usr/sbin/serveradmin stop mysql          

sudo /usr/sbin/serveradmin settings mysql:databaseLocation = /path/to/new/ database/      

sudo /usr/sbin/serveradmin start mysql                     

To set/change the root password:      

sudo /usr/sbin/serveradmin stop mysql          

sudo /usr/sbin/serveradmin settings mysql:rootPassword = password          

sudo /usr/sbin/serveradmin start mysql                     

To start Tomcat:         

$ sudo /Library/Tomcat/6.0/bin/startup.sh                

Open Terminal and enter the following command.   

$ sudo serveradmin settings web:IfModule:_array_id:mod_ssl.c:SSL PassPhraseDialog=builtin              

Start Apache with the command:      

$ sudo serveradmin start web 

When prompted, enter the certificate passphrase.            

To stop Web service:  

$ sudo serveradmin stop web

To see if Web service is running:       

$ sudo serveradmin status web           

 To see complete Web service status: 

$ sudo serveradmin fullstatus web                

To view log paths:      

$ sudo serveradmin command web:command = getLogPaths                     

To see if Web service is running:

$ sudo serveradmin status web 

To see complete Web service status:

$ sudo serveradmin fullstatus web                      

To change several settings:    

$ sudo serveradmin settings   

web:setting = value    

web:setting = value    

web:setting = value    

[…]      

Control–D            

To view a setting:       

$ sudo serveradmin settings web:setting

 http://bestitdocuments.com/Services.html

 

Comments Off on SUDO quick Reference Guide

Top 5 Policy Issues

To advocate effectively for the industry on core public policy issues that impact directly upon consumers’ use and enjoyment of the Internet, the Counter Intrusion, Inc focuses on these consumer-oriented public policy issues:

  • Identity theft
  • Consumer Privacy
  • Internet Security and Law Enforcement
  • Content Regulation
  • Unsolicited Commercial Email
  • B2B and B2C liability

 

Comments Off on Top 5 Policy Issues

Amount of data each day is unbelievable

Posted in Compliances (1300),Information Rights Management (100) by Guest on the April 28th, 2012

We create terabtyes of data each day it’s like an ocean and each day data we create is wider and and further away, duplicate outdated incorrect corrupted. IT organizations have to get a handle on this. This is how identities are lost and customer confidence is lost.

 

Medium Content Type TB / Yr
High estimate
TB / Yr
Low estimate
Paper Books 39 9
Newspaper 138 26
Office Documents 4500 775
Mass Market Periodicals 500 100
Journals 400 2200
Newletters 200 50
Sub-total    
       
Film Photographs 5000 2500
Cinema 600000 20000
Made for TV films 260000 12000
Direct to video 90000000 60000
X-Rays 30000000 100000
Sub-total    
       
Optical Audio CD 108000 60000
CDROM 400000 25000
DVD 150000 5000
Sub-total    
       
Magnetic Videotape 180000000 130000000
Digital Tape 300000 20000
Mini Digital Videocasssettes 1300000 1000000
Floppy Disk 0.50 0.10
ZIP 1000000 5000
Audio MiniDiscs 10 3
Flash 3000000 275000
Hard-Disk 2800000000000 2100000000
Sub-total    
       
Information Totals    

 

 

Media 2009 (TB)
Surface Web 275
Deep Web 410
Email 10000000
Instant Messaging 160
Total  

 

Comments Off on Amount of data each day is unbelievable

The Measure of Success

Posted in Business (600) by Guest on the April 27th, 2012

Failure teaches us valuable lessons…

At 21, he failed in business.

At 22, he lost a legislative race.

At 26, he fell in love, but his sweetheart died.

At 27, he had a nervous breakdown.

At 36, he lost a congressional race.

At 45, he lost a Senate race.

At 47, he failed in a vice presidential bid.

At 52, he was elected president of the United States.

His name: Abraham Lincoln:

Examining your losses is a valuable tool in learning how to win.

“When you don’t get the results you want, you have to ask yourself,

‘What can I learn from this?’

“Past failures may be a gift in disguise.”

  

Lincoln learned a great deal from his failures.  Great thinkers do. They take risk. They sometimes take falls, but truly great ones learn from these failures and go on to be successful.

Thomas Edison conducted more than 700 experiments trying to invent the electric light bulb. “He was once asked if he was discouraged by 700 unsuccessful attempts.

“He replied: ‘I wasn’t discouraged, because every wrong attempt was another step forward.  I learned 700 ways not to make a light bulb.’

In management, we should learn from our mistakes and focus on our successes. Like Edison, I believe I have learned 200 ways not to supervise a team, but along the way I have learned what works.

http://www.bestitdocuments.com/Services.html

 

Comments Off on The Measure of Success

Mobile Email Requirements

Posted in eMail (66),Policies - Standards (600) by Guest on the April 26th, 2012

Scope (Informative)
Mobile e-mail is defined as an e-mail service optimized to support e-mail usage in mobile devices and mobile networks.  This document describes various use cases to illustrate key mobile e-mail usage patterns and will also provide a comprehensive set of high level requirements that can be derived from the use cases.  High-level requirements can be used as a basis for more detailed architecture definition work.

Use cases and high level requirements are defined and described in a technology agnostic way and as such no specific technology implementation is suggested.
 
This Requirements Document focuses on requirements for the enabler specifications rather than for particular implementations of those.  Whether the described features are optional or mandatory for implementations will be decided at a later stage.
 
References
 
Normative References
 

[RFC2119]
“Key words for use in RFCs to Indicate Requirement Levels”, S. Bradner, March 1997, URL:http://www.ietf.org/rfc/rfc2119.txt
[RFC2822]
“IETF Internet Message Format”
(http://www.ietf.org/rfc/rfc2822.txt)
[RFC2045]
“Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
(http://www.ietf.org/rfc/rfc2045.txt)

Terminology and Conventions
Conventions
 
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in [RFC2119].
 
All sections and appendixes, except “Scope” and “Introduction”, are normative, unless they are explicitly indicated to be informative.

Definitions

Mobile E-Mail
Enabling technologies that facilitate end-to-end application level interoperable e-mail transactions (e.g. submission, retrieval, notification etc) to and from mobile devices.
E-Mail Events
Changes to the status of an e-mail (e.g. read/unread, flagged, deleted, etc…) that result for example from reading, moving, deleting etc an e-mail. They may be server or client side events depending on where the change takes place
Email Message
A sequence of data containing a Header and optionally:
A Body,
Meta data
Email Message Headers and Bodies are defined in [RFC2822] “Internet Message Format”
Header
A sequence of lines of characters whose syntax includes a field name followed by a colon (“:”) and followed by a field body. Mandatory Headers included in e-mails are  ‘To:’ and ‘From:’
Headers can also include additional custom end-to-end message headers
Source: IETF [RFC2822] “Internet Message Format”.
Body
A body consists of one or more parts that follow the header. A body could include a combination of some or all of the following:
[RFC2822] defined plain text parts
[RFC2045] defined MIME parts, e.g. inline multimedia content (e.g. SMIL, HTML)
Attachment(s)
Attachment
A special body part within the message body.  Attachments can be displayed in-line or separately based on the indicated presentation semantic, e.g. graphics or word processing files.
Meta Data
Machine-generated attributes applied at delivery time appearing in [RFC2822] header fields. Examples include “RESENT” header field, Message Context (voicemail, email, MMS, SMS) and Processing Rules results.
Filtering Rules
A set of actions and conditions where the conditions are evaluated to determine what e-mail events and what e-mail notifications should be sent from the client to the server or the server to the client. They also include rules to select what new e-mails should be delivered from the server to the mobile client. This may be based on several criteria like subject, date, sender, folder where it is located etc…
Processing Rules
Actions and conditions that are applied on new e-mail. They include: spam prevention, filtering rule, antivirus processing and other scans, attachment removal
Server to Client Notification
A means by which the server informs the client of status changes, e.g. a new message has arrived.

Requirements 
Unless otherwise stated, all requirements apply to the Mobile E-mail Enabler
High-Level Functional Requirements

Label
Description
HLF-1
It MUST be possible to minimize delays and bandwidth requirements (e.g. by minimizing the number of roundtrips between client and server, the bytes to exchange between client and server, etc…) for the following:
o Events sent from the server to the client  or accessed by the client to announce or describe new e-mail
o Exchanges to deliver new e-mail from the server to the client
o Events sent from the server to the client to announce or describe e-mail events on the server
o Events accessed by the client from the server to announce or describe e-mail events on the server
o Exchanges to reconcile the client after a e-mail event on the server
o Exchanges to access or manipulate attachments
o Sending e-mail from an assigned e-mail server
o Sending e-mail events on the client to the e-mail

Table 1: High-Level Functional Requirements
Security

Label
Description
SEC-1
Events sent from the e-mail server to the client to announce or describe new e-mail MUST support confidentiality and integrity.
SEC-2
When used, events accessed by the client from the server to announce or describe new e-mail MUST be end-to-end confidential when desired.
SEC-3
Exchanges to provide new e-mail arrived on server to the client MUST be end to en
d confidential when desired.
SEC-4
When used, events sent from the server to the client to announce or describe e-mail events on the server MUST be end-to-end confidential when desired.
SEC-5
When used, events accessed by the client from the server to announce or describe w-mail events on the server MUST be end-to-end confidential when desired.
SEC-6
Exchanges to reconcile the client after an e-mail event on the server MUST be end to end confidential when desired.
SEC-7
Exchanges to access or manipulate attachments MUST be end to end confidential when desired.
SEC-8
Exchanges to send e-mail from the assigned e-mail server MUST be end to end confidential when desired.
SEC-9
E-mail events sent from the client to the e-mail server MUST be end-to-end confidential when desired.
SEC-10
The client MUST be able to be authenticated by the server when requesting data from the e-mail server.
SEC-11
The server MUST be able to be authenticated by the client.
SEC-12
Mobile email MUST support content screening.
SEC-13
The mobile e-mail enabler MUST allow the mobile client to be protected by the same spam protection solutions as applied on the server.

Table 2: High-Level Functional Requirements – Security Items

NOTE: When desired is used in the mobile e-mail RD in association to security requirements to emphasize the fact that seeking confidentiality of the exchanges between the client and the server MUST be supported when mandated by the actors BUT that it may be okay not to support them in cases where such additional confidentiality assurance is not required or desired.

For example, consumer internet email does not provide such extra confidentiality. In such cases, it may not be needed to provide it with mobile e-mail. Corporate e-mail requires such confidentiality. Therefore the requirement on the enabler is a MUST.
Charging
Charging is not intrinsic to the mobile e-mail enabler.

Label
Description
CHRG-1
In order to support charging for e-mail traffic, the mobile e-mail enabler SHOULD provide ways to identify mobile e-mail exchanges (events, access, sending, synchronization) as e-mail data exchanges, even when the exchanges are end-to-end secure.

Table 3: High-Level Functional Requirements – Charging Items
Administration and Configuration

Label
Description
ADMIN-1
It MUST be possible to provision the mobile client from the server upon authentication and authorization of the user and pairing with a device.
ADMIN-2
It SHOULD be possible for user preferences/filters/settings to follow the user across devices, when desired by the user or administrator.
ADMIN-3
Authorized principals MUST be able to configure the settings of the user preferences/filters/configurable settings for a particular user.
ADMIN-4
The mobile email enabler MUST support preventing or remotely revoking unauthorized usage of and access to e-mail data of a mobile device.

Table 4: High-Level Functional Requirements – Administration and Configuration Items
Usability

Label
Description
USAB-1
Mobile email SHOULD minimize event propagation delays and must not impose excessive delays according to user preferences.
USAB-2
Mobile email SHOULD minimize delays in accessing email messages and must not impose excessive delays according to user preferences.
USAB-3
When / if downloading an attachment, the client SHOULD be able to provide indication of the download and to estimate of the time needed to complete the download.
USAB-4
E-mail sent from client MUST be sent to the e-mail server according to user preference if configurable or client settings otherwise, when network connectivity is available.
USAB-5
When connectivity is not available or drops, if it is possible to compose and sent e-mail, it MUST be stored on the client until connectivity becomes available and then sent to the e-mail server as soon as possible.
USAB-6
 E-mail events on the client to the e-mail server MUST be sent to the e-mail server according to user preferences if configurable or client settings otherwise, when network connectivity is available.
USAB-7
When connectivity is not available or drops, email events on the client that may take place MUST be stored on the client until connectivity becomes available and then sent to the e-mail server as soon as possible.
USAB-8
The mobile email enabler MUST provide support for the user to be able to set filtering rules for the delivery of  email based on:
o Email header fields
o Mailbox folder options.
o Server-determined spam score, Other criteria as needed.
USAB-9
The mobile email enabler MUST provide support for the user to be able to change filtering rules from his mobile client.
USAB-10
Rules (like filtering rules, processing rules, attachment removal, spam prevention, …) applied on the server MUST still apply to the repository on the client for what the user has selected to synchronize on the client.
USAB-11
 The mobile email enabler MUST provide support for the user to be able to select the default or available ways to be notified about new e-mails based on capabilities of client and network:
o what
notification is used (e.g. SMS, Push, MMS, …)
o if events are accessed by client (when, how, what is initially part of the event)
USAB-12
The mobile e-mail enabler MUST support the use of a number of different means to transport notifications (e.g. SMS, MMS, WAP Push, SIP Notification, UDP, in band, polled, …). This will allow. deployment on any target networks.
USAB-13
The User MUST be able to select how e-mail server should present new e-mail events to the client and to select how the client reacts to such events and therefore how the new e-mail is reflected in the client repository:
o  A few meta-data, no stored e-mail
o  A given size of the e-mail
o The whole e-mail without attachment
o The whole e-mail with attachment
USAB-14
The user MUST be able to manually initiate access to e-mail that has arrived on the server but is not yet on the client.
USAB-15
The user MUST be able to manually access more e-mail data when only a portion is stored on the client (e.g. more of the body, a specific attachment, more of a specific attachment, the rest of the body, the whole e-mail with all attachments).
USAB-16
 Authorized principals MUST be able to select the default or available ways that -mail events are sent to or accessed by the client and other e-mail settings that may affect the server behaviour.
USAB-17
The mobile e-mail enabler SHOULD NOT require repetitive actions by the user to provide robustness to intermittent or unreliable connectivity (e.g. loss of connectivity, loss of network transport packets and reconnect) (e.g. having to initiate client reconnect, initiation of synchronization, password entry for server authentication, VPN re-establishment, etc…).
USAB-18
The mobile email enabler MUST enable the user to  forward an e-mail with attachment without downloading the attachment to the client.
USAB-19
The mobile email enabler MUST enable the user to forward an e-mail partially downloaded without having to download the remainder to the client.
USAB-20
The mobile e-mail enabler SHOULD minimize the amount of information that a user must provide to provision an e-mail client to access the appropriate e-mail server.
USAB-21
The client MUST allow the user to reply to an e-mail partially downloaded without first having to download the remainder of the e-mail to the client.
USAB-22
The client MUST allow the user to edit a partially downloaded e-mail, for reply and have the resulting e-mail sent from the server.
USAB-23
 The client MUST allow the user to edit a partially downloaded e-mail , for forward and have the resulting e-mail sent from the server.
USAB-24
The client MUST be able to download body parts or parts thereof that the user wants to edit when replying to an e-mail partially downloaded to the client.
USAB-25
The client MUST be able to download body parts or parts thereof that the user wants to edit when forwarding an e-mail partially downloaded to the client.
USAB-26
When replying to a long list of addressees, the client MUST allow the user to edit the addresses.
USAB-27
Mobile-email Enabler SHOULD support multiple email accounts.
USAB-28
Mobile-email Enabler MUST support configuration of email account information for connection and filtering on a per-account basis.
USAB-29
Mobile-email Enabler SHOULD support definition of auto-reply messages for filtered messages. Automatically generated replies MUST conform to RFC 2821 and related RFCs and MUST NOT lead to mail loops.
USAB-30
Mobile-email Enabler SHOULD support activation/deactivation of auto-reply from the client. Automatically generated replies MUST conform to RFC 2821 and related RFCs and MUST NOT lead to mail loops.
USAB-31
Mobile-email Enabler MUST support replying to messages by using the email account that the original message was received on.
USAB-32
Mobile-email Enabler SHOULD support organization of the retrieved email messages according to their source email account.
USAB-33
The mobile enabler MUST support the user ability to forward only a selection of the attachments of an e-mail with attachments, without downloading the attachments to the client.
USAB-34
The mobile e-mail enabler MUST provide mechanisms to access any desirable email part even when the email size is beyond the limit imposed on the size of the emails that can be delivered to mobile devices while remaining within the size constraints of the part to be downloaded

Table 5: High-Level Functional Requirements – Usability Items
Interoperability

Label
Description
IOP-1
Data exchanges between the client and server, such as Events, sending Mail, reconciliation, attachment manipulation MUST remain functional in the presence of firewalls between the mobile e-mail client and the users e-mail servers.
IOP-2
When used, events sent from the server to the client to announce or describe new e-mail MUST be network neutral.
IOP-3
When used, events accessed by the client from the server to announce or describe new e-mail MUST be network neutral.
IOP-4
Exchanges to provide e-mail arrived on server to the client MUST be network neutral.
IOP-5
Exchanges to reconcile the client after a e-mail event on the server MUST be network neutral.
IOP-6
Exchanges to access or manipulate attachments MUST be network neutral.
IOP-7
It MUST be possible to send e-mail from the e-mail server assigned to the user (e.g. not another SMTP server in another domain).
IOP-8
Sending e-mail from an assigned e-mail server MUST be network neutral.
IOP-9
Sending e-mail events on the client to the e-mail server MUST be network neutral.
IOP-10
The mobile e-mail enabler MUST allow the e-mail repository on the mobile client to be synchronized with the appropriate backend server:
· Sometimes via the OMA Mobile e-mail enabler specifications (between client and server)
· Sometimes via the OMA DS specifications for e-mail between the client and another client, that it be
o Connected to the server
o Previously synchronized with the server and later re-synchronized with the server
IOP-11
The e-mail enabler MUST support server-side adaptation of attachment to the device user by user.
IOP-12
The server-side adaptation MUST be capable of being controlled by the client (e.g., with smart or intermediate clients).
IOP-13
The design of the mobile e-mail enabler specifications SHOULD consider and aim at interoperability or gracefully degradation with relevant e-mail standards.
IOP-14
The number of optional features in the Mobile E-mail enabler specifications SHOULD be minimised, while allowing efficient implementation of both consumer and enterprise mobile e-mail solutions.
IOP-15
Server-side adaptation MUST preserve the ability of accessing e-mail via other channels (e.g. via other e-mail clients).
IOP-16
Server-side adaptation MUST preserve the original e-mails and attachment stored in the e-mail server

Table 6: High-Level Functional Requirements – Interoperability Items
Privacy

Label
Description
PRIV-1
The mobile e-mail enabler MUST allow the mobile client to be protected by the same privacy protection rules / solutions as applied on the server (e.g. filtering rules, privacy alert detections on outgoing e-mail, read/unread notice interception).
PRIV-2
The mobile e-mail enabler MUST support the use of privacy tools that require user’s confirmation before allowing some e-mail events to take place.

Table 7: High-Level Functional Requirements – Privacy Items
 
Overall System Requirements

Label
Description
SYSREQ-1
The mobile e-mail enabler MUST be robust enough to operate normally and useably when there is a intermittent or unreliable connection between the client and server.
SYSREQ-2
The mobile e-mail enabler security (authentication, authorization, confidentiality, integrity) MUST operate and be usable in the presence of intermittent or unreliable connectivity (loss of connectivity, loss of network transport packets and reconnect).
SYSREQ-3
The mobile e-mail enabler MUST NOT rely on the storage of email data in intermediate systems outside the e-mail server domain or the terminal.
SYSREQ-4
Mobile e-mail enabler MUST permit highly scalable end-to-end implementations.
SYSREQ-5
The mobile e-mail enabler SHOULD allow optimized implementations on constrained devices (e.g. power consumption, CPU overhead, memory and storage requirements).

 http://www.bestitdocuments.com/Networking.html

 

Comments Off on Mobile Email Requirements

Sample Visio – Icons 2

Posted in Application (380),Visio Samples - Stencils (457) by Guest on the April 26th, 2012

 Free – Visio Document download

Icons 2

http://www.bestitdocuments.com/Services.html

 

Comments Off on Sample Visio – Icons 2

Sample Excel Really Good – IP Addressing Workbook Spreadsheet

Comments Off on Sample Excel Really Good – IP Addressing Workbook Spreadsheet

Sample Visio – Server drawings

Comments Off on Sample Visio – Server drawings

Protecting Against Spyware and Adware

Posted in eMail (66) by Guest on the April 23rd, 2012

If you notice any of the following symptoms, you may have adware or spyware installed on your computer:

  • Noticeable slowdown in performance with no other explanation.
  • Unusual software behavior, such as your Web browser’s home page suddenly changing, new items appearing in your Favorites menu, or programs closing unexpectedly.
  • Strange hardware behavior, such as the CD drive opening or unusual hard drive activity.
  • Strange network behavior, such as indications by your modem lights that your computer is transmitting data when you are not doing anything online.
  • Pop-up ads displaying when you are not surfing the Web. 

Protecting Against Unwanted E-mail

  • Unwanted e-mail, like junk mail in physical mailboxes, probably can never be completely eliminated. However, there are several things you can do to reduce the amount of spam you receive, including general spam protection practices, using spam filtering services or software, and using sender verification systems.

General Spam Protection Practices

  • Do not give out your e-mail address indiscriminately. Spammers often collect addresses from Web forms or buy them from organizations that collect the information. When you fill out online registrations (for example, many online news sites require that you register before you can read the stories), leave the e-mail address blank or provide an alternate address.
  • Using Spam Filtering Services and Software
  • Using E-mail Sender Verification

Making Web Browsing More Secure

  • Many exploits, malware programs, spam schemes, and phishing scams make use of the Web to collect information. Early Web pages consisted of just text and graphics, but now sophisticated Web sites use programming embedded in the Web pages to create amazing special effects. These capabilities also create security issues.

You can make Web browsing more secure by doing a few simple things:

  • Keep all security patches and service packs for your Web browser and operating system up to date.
  • Configure your browser’s security settings for safe browsing.
  • Configure your browser’s privacy settings to avoid unwanted cookies and pop-up ads.
  • Be careful about which Web sites you visit. Sites devoted to illegal or questionable subjects, such as hacker sites, sites for downloading pirated music or software, and pornographic sites are most likely to contain malicious code.
  • Enable checking of digital signatures on drivers and other programs you download.
  • Do not conduct financial transactions or send private information over the Web unless the site is secure (which is usually indicated by a dialog box or a “lock” icon in the browser’s status bar).
  • Configure your browser to not automatically download ActiveX controls, or run scripts, Java applets, or other code. If you want to be able to run code on some sites, configure the browser to prompt you before doing so. 

You can adjust the security settings for your Web browser software to make Web browsing more secure

  • You can test your Web browser software for common vulnerabilities and determine its encryption strength most corporation and ISP provide Internet assistance and advice in this area. Consult with your ISP or IT department for assistance.

Note: Some organizations’ IT policies specify that updates and patches only be installed by the IT department. Organizations may delay deploying service packs and other updates because of conflicts with proprietary software. Do not download or install software of any kind, including updates, and do not change the automatic update settings on any computer owned by the organization without the knowledge and permission of the IT department.

http://bestitdocuments.com/Services.html

 

Comments Off on Protecting Against Spyware and Adware

A simple view of a Security Assessment

Posted in Security (1500) by Guest on the April 22nd, 2012

A security consultant identifies the security posture of your network information assets as it relates to external and internal threats. With a focus on Vulnerability and Exploitation testing of mission-critical hosts, servers, network equipment, firewalls, leased lines and your companies Internet Point of presence with automated, repeatable tests to identify security vulnerabilities. Experienced and trained security experts should evaluate your existing security practices, recommend an action plan, and provide documentation that forms the basis for an ongoing protection program designed to meet your organization specific needs:

  1. Benchmarking of your current security practices against industry best practices
  2. Consultation from operating systems, applications, and infrastructure component experts who evaluate your current security posture, develop guidelines, and recommend improvements
  3. A variety of service options including penetration testing, vulnerability analysis, host assessment,  risk assessment, and more
  4. Utilization of the latest security methodologies and technologies
  5. Support for multi-vendor products

 

Security Planning, Design and Implementation

A security consultant designs a security solution that best meets your needs and facilitates the procurement and installation of network components. Your security consultant Information Security practice designs and implements security systems using sophisticated off-the-shelf products in custom configurations to enforce the specific Information Security Policy of each client. These systems are designed to assist users in the proper use of corporate information systems, while restricting and preventing possible misuse. When combined with an effective personnel management practice that emphasizes responsible information handling by all employees, the confidentiality, integrity, and availability of critical information assets is measurably improved. 

Your security consultant advisor provides quick and efficient deployment and migration of a secure, reliable network are critical to remain competitive in today’s marketplace. Your security consultant advisor provide the technical expertise you need to help quickly and flawlessly design, deploy or migrate your network, with best-in-class solutions designed to meet your specific security requirements and provide a high return on your investment. We utilize proven, structured approaches to maximize operational efficiencies and reduce costs while minimizing the impact on your organization:

  1. Planning, design, implementation, and operation of secure network architectures combining best-in-class security products with your business requirements and corporate policies
  2. Utilization of highly trained security experts
  3. Consultation on areas of specialization, including Public Key Infrastructure (PKI), authentication services, Virtual Private Networks (VPNs), Intrusion Detection Systems (IDS), secure remote access, firewalls, and more
  4. Analysis of your business drivers and security requirements with solution recommendations that promote the successful integration of best-in-class products into your environment
  5. Migration of security components with minimal impact on your current operations
  6. Knowledge transfer through the involvement of your staff in the implementation and operations phase of your project
  7. Utilization of the latest security methodologies and technologies
  8. Support for multi-vendor products

http://bestitdocuments.com/Services.html

 

Comments Off on A simple view of a Security Assessment

Sample Visio – SAML 2.0 Login / Logout

Comments Off on Sample Visio – SAML 2.0 Login / Logout

Sample Visio – CMMI V2.0

Posted in Business (600),Security (1500),Visio Samples - Stencils (457) by Guest on the April 21st, 2012

 Free – Visio Document download

CMMI V2.0

http://www.bestitdocuments.com/Services.html

 

Comments Off on Sample Visio – CMMI V2.0

eMail Security tidbits – Things that will surprise you !

Posted in eMail (66) by Guest on the April 21st, 2012

 Interesting eMail Security tidbits of information:

  • E-mails, contracts, and PowerPoint files account for 80 percent of corporate information.
  • 71% Use Email to Negotiate Contracts and Agreements
  • 69% Use Email to Exchange Invoices, Statements, and Payment Information
  • 93% Use Email to Communicate with Customers.
  • 38% Use Email to Respond to Regulators
  • 44% Use Email to File with Official Bodies
  • 35% Use Separate Back-End System for Email Retention
  • 23% Use Records Management System for Managing Email
  • 34% Use Document Management System for Managing Email
  • 40% Use Email Management and Archiving Software

There are currently over 10,000 U.S. federal, state, and local laws and regulations addressing what, how, when and why records must be created, stored, accessed, maintained, and retained over increasingly longer periods of time.

The Education sector accounted for the majority of data breaches with 30%, followed by Government (26%) and Healthcare (15%) – almost half of breaches (46%) were due to theft or loss with hacking only accounting for 16%.

Hacking resulted in 73% of identities being exposed

  • 1:400 emails contain confidential information
  • 1:50 network files are wrongly exposed

Breaches on the rise

  • 2010:142 companies exposed 86M individual data records
  • 2010: In 6 months, 40 companies and government agencies have exposed nearly 30M individual data records

IT Professionals need to address mission-critical administration concerns with in-depth, concise coverage. Some sample topics would be:

  • Defending the company’s sensitive information against security problems
  • Neutralizing the threat of computer viruses
  • Identifying potentially disastrous hardware conflicts
  • Unlocking the hidden usefulness of Windows NT utilities
  • Creating seamless Windows NT and Unix interoperability
  • Integrating emerging Internet technologies with your network
Comments Off on eMail Security tidbits – Things that will surprise you !

Sample Visio – ASP – Based Model of Providing Services

Comments Off on Sample Visio – ASP – Based Model of Providing Services

Sample Visio – SAML 1.1 vs SAML 2.0 short view

Comments Off on Sample Visio – SAML 1.1 vs SAML 2.0 short view

What you should look for when shopping for a Data Center

A wide range of state of the art facility and IT technology characteristics these characteristics include:

  • Earthquake suppression (structural design),
  • Lightning suppression,
  • Tornado and flood suppression,
    • Moisture detection,
    • Sealed conduits,
    • Sump pumps,
    • Drainage 
  • Power distribution and backup power supply,
  • Flywheel CPS (continuous power supplies),
  • Surge protection and brownouts,
  • Redundant backup diesel generators,
  • Redundant UPS protected power circuits,
  • Water cooled redundant package chillers,
  • Environmental controls air quality control systems,
  • Raised floors,
  • Fire detection and suppression
  • Smoke and carbon dioxide detection units,
  • Tightly controlled customer access via a security lobby,
  • Customer-operated environmental control,
    • Role based access controls,
    • Biometric geometry scanners,
    • Monitoring / audit controls,
  • Highly secure physical monitoring,
  • Server thermal monitoring,
  • Motion detectors and alarms,
  • Silent alarms,
    • Exterior CCTV high resolution / night vision image recorders
    • CCTV image recorders 

Highly secure monitoring,

  • Lockable cabinets with direct access,
    • Private cabinets
    • Shared cabinets 
  • Global Tier 1 / Tier 2 network neutral services provide direct interconnection to the largest aggregation
    • Interconnectivity – With direct access to the top global Tier 1 / Tier2 networks, network neutral services provide direct interconnection to the largest aggregation of networks for unmatched service diversity, flexibility and reliability. 
  • Enterprise Class firewall edge services
  • Enterprise class Network routing and switching infrastructure
  • Enterprise load balancing and clustering
  • Enterprise class IPS / IDS edge services
  • Enterprise VPN services
  • Enterprise Asset management / tracking
  • Enterprise IP Management
  • Enterprise data backup services
    • Enterprise server snap imaging and recovery
  • Enterprise storage services
  • Enterprise recovery services
  • Enterprise IT (ITIL) control services and change controls

The facility should separate the welcome lobby from the operations center staffed 24*7 with security officers, a customer care area staffed with engineers and technicians ready to solve problems, and a secure separate shipping and receiving area.

 http://www.bestitdocuments.com/Help-desk_solutions.html

 

Comments Off on What you should look for when shopping for a Data Center

Sample Word – Sample Data Classification Policy

Posted in Compliances (1300),Security (1500) by Guest on the April 19th, 2012
Comments Off on Sample Word – Sample Data Classification Policy

Sample Visio – What is a an IT Process

Free Visio Document Download

What is an IT process and how does this might fit in your processes.

What is a Process

http://www.bestitdocuments.com/Services.html

 

Comments Off on Sample Visio – What is a an IT Process

Sample Visio – ITIL – Crisis Management Team Structure

Comments Off on Sample Visio – ITIL – Crisis Management Team Structure

IT Architecture Principles

Posted in Application (380),Compliances (1300),Security (1500) by Guest on the April 18th, 2012

Just another opion of many that are out on the Internet.

Architecture guides planning, design, implementation and testing and identifies key principles to be applied to the solution design. The architecture decision documents helps to maintain a record of the important decisions made during the development of the broader Enterprise Architecture. A well documented architecture decision includes it’s own justification and evaluation criteria. 

Architectural decisions could relate to important decisions about all aspects of architecture including the structure of the system, the provision and allocation of function, the contextual fitness of the system and adherence to standards. It will contain the reasoning for each of the decisions and where necessary reference external documents that further explain the recommendation / decisions. 

Purpose

The purpose of the architectural decision document is to:

  1. Record important architectural decisions, with relevant standards, policies and evaluation criteria
  2. Make explicit the rationale and justification of the decisions
  3. Enforce standards, policies and the need for broader review that lead to consistency and alignment across business and architectural goals and priorities
  4. Provide a reference of documented decisions for new people who join the project or for interested stakeholders
  5. Avoid unnecessary reconsideration of the same issues

Outcomes

The architecture decisions document can be used either to deal with individual decisions that are required (including architectural reviews) or as a record of all architecture decisions made within a project. This is typically determined by the Enterprise / Project Architecture and / or the project manager. 

The Enterprise decision document can be used for maintaining a final copy of all architecture decisions for future reference. However, a non-authoritative copy of an Architecture Decisions document developed for project work should also exist in the set of project documentation artifacts.

http://www.bestitdocuments.com/Services.html

 

Comments Off on IT Architecture Principles

Sample Word – Data Center Cabling Installation Standards

Free Word – document download

This document was pieced together from Internet resources for a Data Center build project and is focused on cabling.

Cabling Installation Standards

http://www.bestitdocuments.com/Operating_system.html

 

Comments Off on Sample Word – Data Center Cabling Installation Standards

Sample Visio – Icons 1

Posted in Application (380),Visio Samples - Stencils (457) by Guest on the April 17th, 2012

 Free Visio Document Download

Icons 1

http://www.bestitdocuments.com/Services.html

 

Comments Off on Sample Visio – Icons 1

CA eHealth Pilot Project Sample Requirements

Technical Startup

  • Perform engagement management setup activities
  • Prepare for engagement
  • Review implementation information with customer
  • Review project schedule with customer 

Architecture and Design

  • Conduct briefing with customer project sponsor
  • Conduct kick-off session
  • Gather project related information and requirements
  • Document requirements
  • Modify test plans as required
  • Review implementation plan with customer 

Implementation

  • Install/configure eHealth Suite
  • Install/configure Spectrum Server
  • Install/configure OneClick Clients
  • Install/configure LiveHealth
  • Install/configure SystemEdge
  • Install/configure Service Availability 

Major Technical Activities

  • The following high-level activities will take place during this engagement 
    • Architecture Review and Planning
      • Review implemented architecture, revise and update as required
      • Expand architecture to incorporate remote locations
      • Discuss obtaining system and network performance metrics 
    • Technical Assumptions
      • Needed access to all hosts, systems, and network devices as necessary for the installation of required software.
      • All prerequisite hardware and software will be available on-site prior to project start.
      • All hardware will meet the system requirements for the product
      • IT staff available on an as-needed basis for assistance in troubleshooting and to receive knowledge transfer.
      • Identified requirements for instrumentation and notification
      • Network and Firewalls rules in place to support product communication flows
      • All SNMP Read Only Community Strings are the same across all network devices 
    • Solution Phases and Technical Milestones
      • This engagement will be implemented using the following phases and milestones: 
    • Project Schedule Reviewed with Customer
      • The technical startup phase will launch the project by preparing the project plan and schedule, and obtaining customer acceptance on both documents.
      • Prepare and deliver a Solution Architecture Specification for this solution. 
    • Implementation Plan 
    • Phase I – Installation
      • Install eHealth Suite Server
      • Install Spectrum Server
      • Install OneClick Clients
      • Install LiveHealth
      • Install SystemEdge 
    • Phase II – Configuration
      • Configure eHealth Server
      • Configure Spectrum Server
      • Configure OneClick Clients
      • Configure LiveHealth
      • Configure SystemEdge and AIMs
      • Configure Service Availability
      • Customize and Schedule specific reports
      • Completion of Test Plan
      • The completion of the execution of the test plan will be confirmed by obtaining customer acceptance of the completed test plan.
      • Implemented Components in Production
      • The components identified in the implementation plan are placed in production in turn as specified in the plan.
      • Complete Review of Implementation
      • The users of the new system have been trained and the complete solution has been reviewed with the customer.  
    • Technical Closure
      • Conduct knowledge transfer for existing CA Network and Systems Management solution on new reporting capabilities
      • ‘Train the Trainer’ sessions for Pilot contacts in preparation for educating their customer base
      • Review implementation with Pilot contacts
      • Conduct final review session with Pilot contacts
Comments Off on CA eHealth Pilot Project Sample Requirements
Next Page »