27.06.2013 Views

6th European Conference - Academic Conferences

6th European Conference - Academic Conferences

6th European Conference - Academic Conferences

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Mecealus Cronkrite et al.<br />

with security requirements for government information systems. Security rests with the acquisition<br />

policy and contract, vendor management controls that they defined, a non-standard approach.<br />

However, the GAO has found that the federal government overall has major deficiencies information<br />

security. Mainly due to the lack of technical acquisition expertise needed to interpret and apply security<br />

requirements to contracts and the rigor and sustaining efforts required to keep validating vendor<br />

quality. (GAO-09-661T, 2009) Therefore increasing the federal IT workforce and capabilities, DHS<br />

NCCD can start to upgrade and improve the performance of security within the US government. Security<br />

requirements should be equally valued and balanced as e-government requirements in order to<br />

improve CI defence from disasters and attacks. Moreover, adding vendor non-compliance fines in the<br />

government IT acquisition process should increase the attention paid to CI systems.<br />

5. Conclusions and future work<br />

There is a growing relationship between preventable software assurance failures and exposed critical<br />

cyber infrastructure risk. Preventable software defects remain unresolved at the peril of all software<br />

consumers and endanger the cyber infrastructure on which we all rely. The software consumer is uninformed<br />

and cannot self assure that the outsource software they order meets an acceptable standard.<br />

Making the security case clear enough to the public to understand is harder than making the<br />

case to the developer and the business manager through market forces.<br />

The growing black market economy of malware is exploiting the existing known defects in widely distributed<br />

commercial software. Targeting known common software defects is a primary vector to enter<br />

trusted networks and systems. Preventable programming errors make “zombie” slave computers accessories<br />

to organized crimes. The growing criminalisation of cyber attacks is driving the need for<br />

new controls in the previously unregulated software development culture.<br />

Without support, the business will tend to favour of profits over safety. It is the nature of profit motivation.<br />

Firms on their own will not decide to invest the socially optimal amount in cyber security because<br />

it conflicts with their own rational decision making criteria. However, by supported standards it enables<br />

the developer and publisher to mitigate preventable risk.<br />

Improving software assurance practices is one of the key countermeasures for protecting critical infrastructure.<br />

The industry needs to be motivated to encourage accountability and liability on behalf of<br />

the public good by avoiding common errors. This would also raise the barriers to entry on the software<br />

development market and ease the pressure on existing competitors who are able to adopt assurance<br />

practices, while legitimatizing IT as a new profession responsible for entrusted with the public good<br />

defending the critical cyber infrastructure.<br />

The proposed approaches examined a framework of increasing government and private controls on<br />

software quality and software assurance outcomes.<br />

Mandate Cyber Incident Reporting for CI industries to increase transparency and research ability.<br />

Enforce (Fines) for Federal IT Security development Non-Compliance to create better vendor<br />

compliance.<br />

Create better IDE tools that check for common programming errors, to help prevent the programmer<br />

from making common errors, and increase the resilience of the software infrastructure.<br />

Encourage professional licensing and non-repudiation for CCI Developers and Publishers to help<br />

to increase accountability and transparency in the publisher and developer community.<br />

The software industry will not be able to negotiate the safety standards process alone, without some<br />

government assistance. There is a need for standards based software professional accreditation to<br />

ensure the consistent application of basic security programming techniques and data privacy. However,<br />

the industry should not wait for legislation. Software publishers have the ability to seize the momentum<br />

of media awareness and establish accountability for code security within their corps.<br />

Acknowledgements<br />

This work is an extended study of our final team project of IST623 (Introduction to Information Security),<br />

taught by Prof. Joon S. Park, in the School of Information Studies at Syracuse University in<br />

Spring 2010. We would like to thank the class for valuable feedback, insight, and encouragement as<br />

we researched and developed this project during the semester.<br />

74

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!