$array = $array[1..$array.Length]

<installcontrol>
   <serverlist>
      <server>
         <servername>ALDARAAN</servername>
         <servername>TATOOINE</servername>
      </server>
   </serverlist>
<installcontrol>

$xmlFile = Get-Content $xpath
$objNewServer = $xmlFile.CreateElement("server")
$objNewServerName = $xmlFile.CreateElement("servername")
$objNewServerName.Set_InnerText("DANTOOINE")
$objNewServer.AppendChild($objNewServerName)
$xmlFile.installcontrol.serverlist.appendchild($objNewServer)
$xmlFile.Save("$xpath")

<installcontrol>
   <serverlist>
      <server>
      </server>
    </serverlist>
<installcontrol>

$xmlFile = Get-Content $xpath
$objNewServer = $xmlFile.CreateElement("server")
$objNewServerName = $xmlFile.CreateElement("servername")
$objNewServerName.Set_InnerText("DANTOOINE")
$objNewServer.AppendChild($objNewServerName)
$xmlFile.installcontrol["serverlist"].appendchild($objNewServer)
$xmlFile.Save("$xpath")

& "d:\scripts\installwebserver.ps1"

"Later, Rushing shows me how easy it is for a phisher to duplicate one of these internal 'guest' log-in screens and grab all the traffic from an unsuspecting client. 'I'm surprised we don't see more of that.'"

"'Kids are adding to WIGLE all the time -- it's one of the ways you can look cool,' Rushing says. 'The more APs you've mapped, the cooler you are.'"

A former senior U.S. information security official says there are nearly three-quarter million personal computers in the United States taken over by Chinese hackers.

today the traditional "firewalled" approach to securing a network boundary is at best flawed, and at worst ineffective. Examples include:

-business demands that tunnel through perimeters or bypass them altogether
-IT products that cross the boundary, encapsulating their protocols within Web protocols
-security exploits that use e-mail and Web to get through the perimeter.

to respond to future business needs, the break-down of the traditional distinctions between “your” network and “ours” is inevitable

increasingly, information will flow between business organizations over shared and third-party networks, so that ultimately the only reliable security strategy is to protect the information itself, rather than the network and the rest of the IT infrastructure

While traditional security solutions like network boundary technology will continue to have their roles, we must respond to their limitations. In a fully de-perimeterized network, every component will be independently secure, requiring systems and data protection on multiple levels, using a mixture of:

-encryption
-inherently-secure computer protocols
-inherently-secure computer systems
-data-level authentication

The design principles that guide the development of such technology solutions are what we call our “Commandments”, which capture the essential requirements for IT security in a de-perimeterized world.

The Jericho Forum commandments define both the areas and the principles that must be observed when planning for a de-perimeterized future.
Whilst building on “good security”, the commandments specifically address those areas of security that are necessary to deliver a de-perimeterized vision.
The commandments serve as a benchmark by which concepts, solutions, standards and systems can be assessed and measured.

Conclusion
De-perimeterization has happened, is happening and is inevitable; central protection is decreasing in effectiveness

- It will happen in your corporate lifetime
- Therefore you need to plan for it and should have a roadmap of how to get there
- The Jericho Forum has generic roadmap to assist in the planning

The scope and level of protection should be specific & appropriate to the asset at risk

- Business demands that security enables business agility and is cost effective
- Whereas boundary firewalls may continue to provide basic network protection, individual systems and data will need to be capable of protecting themselves
- In general, it’s easier to protect an asset the closer protection is provided

Security mechanisms must be pervasive, simple, scalable & easy to manage

- Unnecessary complexity is a threat to good security
- Coherent security principles are required which span all tiers of the architecture
- Security mechanisms must scale; from small objects to large objects
- To be both simple and scalable, interoperable security “building blocks” need to be capable of being combined to provide the required security mechanisms

Assume context at your peril

- Security solutions designed for one environment may not be transferable to work in another. Thus it is important to understand the limitations of any security solution
- Problems, limitations and issues can come from a variety of sources, including geographic, legal, technical, acceptability of risk, etc.
- Surviving in a hostile world

& "d:\scripts\installwebserver.ps1" SERVERNAME

Devices and applications must communicate using open, secure protocols

- Security through obscurity is a flawed assumption - secure protocols demand open peer review to provide robust assessment and thus wide acceptance and use
- The security requirements of confidentiality, integrity and availability (reliability) should be assessed and built in to protocols as appropriate, not added-on
- Encrypted encapsulation should only be used when appropriate and does not solve everything

All devices must be capable of maintaining their security policy on an untrusted network

- A “security policy” defines the rules with regard to the protection of the asset
- Rules must be complete with respect to an arbitrary context
- Any implementation must be capable of surviving on the raw Internet, e.g., will not break on any input

All people, processes, technology must have declared and transparent levels of trust for any transaction to take place

- Trust in this context is establishing understanding between contracting parties to conduct a transaction and the obligations this assigns on each party involved
- Trust models must encompass people/organisations and devices/infrastructure
- Trust level may vary by location, transaction type, user role and transactional risk

Mutual trust assurance levels must be determinable

- Devices and users must be capable of appropriate levels of (mutual) authentication for accessing systems and data
- Authentication and authorisation frameworks must support the trust model

Authentication, authorisation and accountability must interoperate / exchange outside of your locus / area of control

- People/systems must be able to manage permissions of resources and rights of users they don't control
- There must be capability of trusting an organisation, which can authenticate individuals or groups, thus eliminating the need to create separate identities
- In principle, only one instance of person / system / identity may exist, but privacy necessitates the support for multiple instances, or once instance with multiple facets
- Systems must be able to pass on security credentials /assertions
- Multiple loci (areas) of control must be supported

$smtp = new-object Net.Mail.SmtpClient("mail.server.com")
$smtp.send("mike@server.com","mike@server.com","test","test")
$smtp


Host : mail.server.com
Port : 25
UseDefaultCredentials : False
Credentials :
Timeout : 100000
ServicePoint : System.Net.ServicePoint
DeliveryMethod : Network
PickupDirectoryLocation :
EnableSsl : False
ClientCertificates : {}

PS> $smtp = new-object Net.Mail.SmtpClient
$smtp.DeliveryMethod = "PickupDirectoryFromIis"
$smtp.send("mike@server.com","mike@server.com","test","test")
$smtp


Host :
Port : 25
UseDefaultCredentials : False
Credentials :
Timeout : 100000
ServicePoint : System.Net.ServicePoint
DeliveryMethod : PickupDirectoryFromIis
PickupDirectoryLocation :
EnableSsl : False
ClientCertificates : {}

Access to data should be controlled by security attributes of the data itself

- Attributes can be held within the data (DRM/Metadata) or could be a separate system
- Access / security could be implemented by encryption
- Some data may have “public, non-confidential” attributes
- Access and access rights have a temporal component

Data privacy (and security of any asset of sufficiently high value) requires a segregation of duties/privileges

- Permissions, keys, privileges etc. must ultimately fall under independent control, or there will always be a weakest link at the top of the chain of trust
- Administrator access must also be subject to these controls

By default, data must be appropriately secured when stored, in transit and in use

- Removing the default must be a conscious act
- High security should not be enforced for everything; “appropriate” implies varying levels with potentially some data not secured at all

tftp 192.168.10.108 -c get c2950-i6k2l2q4-mz.121-22.EA8a.bin

switch: flash_init
Initializing Flash...
...The flash is already initialized.
switch: load_helper
switch: copy xmodem: flash:c2950-i6k2l2q4-mz.121-22.EA8a.bin
Begin the Xmodem-1k transfer now...

According to them, in the next five years the Internet will be the primary connectivity method for businesses, replacing their private network infrastructure as the number of mobile workers, contractors and other third-party users continues to grow.

One of the end results of the death of traditional network security will be a growth in desktop virtualization, Whiteley said.

Desktop virtualization allows a PC's operating system and applications to execute in a secure area separate from the underlying hardware and software platform. Its security advantages have become a major selling point, as all a virtualized terminal can do is display information; if it is lost or stolen, no corporate data would likely be compromised since it wouldn't be stored on the local hard drive.

The adoption of PC virtualization would mean companies would no longer have to provision corporate machines to untrusted users, Lambert said. Desktop virtualization simply equals a more secure environment, she said.

sudo gedit /etc/apt/sources.list

deb http://repository.debuntu.org/ feisty multiverse
deb-src http://repository.debuntu.org/ feisty multiverse

wget http://repository.debuntu.org/GPG-Key-chantra.txt -O- | sudo apt-key add -
sudo apt-get update
sudo apt-get install pidgin
sudo apt-get install pidgin-libnotify