Network Security Library
Javascript Feeds    RSS Feed    Security Dashboard    SearchSecurity.com
About | Contact | Advertise | Site Map

Application Security


{LANG_NAVORIGIN} Application Security

Subcategories


Oracle
PHP and MySQL




Newest Application Security White Papers

Distributed Systems Security: Java, CORBA, and COM+
Security can have varying levels of difficulty for implementation. One factor in determining the difficulty is the number and distribution of the systems. With distributed systems architecture, there are different nodes and resources. One major issue with distributed systems is application security. There is the question of how security is handled in distributed applications, and how the client handles applications coming from an unknown source. The purpose of this paper is to examine three popular architectures for distributed systems applications and their security implications. The architectures analyzed are Java by Sun, CORBA by the OMG, and COM+ from Microsoft. Outstanding issues and future areas for research are considered.
By April L. Moreno, 03/24/2004


Security Scenarios in Analysis and Design
This article addresses the issue of designing security into systems rather than trying to add it to systems after development. It is found by surveying teaching materials that security is only given brief acknowledgement as a concern in software development and that security is not well integrated into development life cycles used in schools.
By Dwight A. Haworth, 03/23/2004


Framework for Secure Application Design and Development
The practice of secure application design and development is an important and necessary attribute of a secure computing environment. Applications that protect data from unauthorized access or modification and ensure its availability are key advantages to companies with physical and information assets that require such an environment. But, as crucial as this practice is, applications often are not being designed and developed with security in mind. As such, these applications are contributing to the burgeoning miasma of potentially insecure interconnected systems providing an open door to the possible compromise of companies' sensitive and valuable information or systems.
By Chris McCown, 03/23/2004


Security for a CRM environment
Customer Relationship Management software has been a buzzword in the Information Technology industry for quite a few years now. Many companies are looking at how CRM can help make them more successful by providing an extensive customer information database in which Sales, Marketing, Service, and other departments can use a variety of ways to better serve the customer. In today's competitive marketplace, good customer service is extremely important. There are many software vendors selling CRM software packages that offer a one-stop solution for gaining marketplace share, manage, and retain customer loyalty to their product. It is note worthy for companies to keep in mind that CRM deals with handling a company's most important resource: Customer Data.
By Jason LaFrance, 03/23/2004


The Bugs are Biting
Currently there are thousands and thousands of software programs running on millions of computers across the world. Yet there are also bugs crawling around the code of these programs that are biting holes into the security of the machines they run on. Unless this issue is seriously addressed in the near future, one can expect to see an increase in the severity and quantity of security breaches. This paper will give a general overview of the problems and challenges of software mistakes and how they affect security.
By Rishona Phillips, 03/23/2004


Application Development Technology and Tools: Vulnerabilities and threat management with secure programming practices, a defense in-depth approach
This paper addresses the security challenges that exist due to programming flaws, and explains how simple programming practices can reduce the risks. The paper starts with a description of common application vulnerabilities and risks. The vulnerabilities that are discussed include Buffer overflows, SQL Injection, Script Injection, XML injection and others. The application development platforms, technologies and tools that are widely used in the industry and the vulnerabilities that exist in them are discussed next. The technology and tools discussed include Web Services, Wireless, JAVA, C/C++, Web and Database. Further, the secure programming practices that can be used to avoid the vulnerabilities are presented. Since more and more organizations are embracing the outsourcing business model, the importance of having good security practices in such an environment is briefly touched upon. In the end, case study examples have been provided to illustrate the use of secure coding principles.
By Vilas L Ankolekar, 03/23/2004


SQL Server 2000: Permissions on System Tables Granted to Logins Due to the Public Role
In this paper I will cover the access rights to system tables the public role has in these two system databases as well as in a typical user database. I'll also cover how the guest user adds to the conundrum, especially with respect to the system databases and cross-database ownership chaining. Finally, I'll look at what permissions can be revoked from the public role in each database and what the consequences are, both from a practical perspective (typical applications) to an extreme example (Microsoft's OpenHack 4 configuration).
By K. Brian Kelley, 03/23/2004


What is SOCKS?
An explanation of the SOCKS protocol (functions, features & benefits) and application proxy gateway systems.
By B. Scott Wilson, 03/23/2004


Instant Insecurity: Security Issues of Instant Messaging
This paper will describe instant messaging and offer a brief overview of some of the security threats associated with the service. This article is based on a previously published Symantec white paper called Threats to Instant Messaging.
By Neal Hindocha , 03/22/2004


Castles Built on Sand: Why Software is Insecure
We have all heard reports of vulnerabilities being discovered in various software. But what actually makes software more or less secure than the rest of its competitors? Theoretically, all software starts in the same place - with the very first sketch on somebody's napkin over dinner. It grows from there; the environment in which it is developed, who controls the project and most importantly who works on the project all contribute to the outcome. Unfortunately, the outcome is not always what the developers had in mind. Many software programs are plagued by programming flaws that may lead to security vulnerabilities. This article will offer a brief overview of some of the factors that may contribute to insecure software.
By Josh Ryder, 03/22/2004


Page: 123456 7 8


Application Security
Architecture
Authentication
Certifications
Disaster Recovery
Encryption
Enterprise Security
Exploits
Firewall
Incident Handling
Intrusion Detection
Laws and Regulations
Malicious Code
Operating System
Security Basics
Security Management
Security Policies
Security Tools
Standards
Vulnerability Management
Web Security
Wireless Security

Newest
Highest Rated
Most Viewed
Reference

Javascript Feeds
RSS (New Papers)
Security Dashboard

About SecurityDocs
Advertise
Contact

Valid HTML 4.01!
Valid CSS!


Unless otherwise noted, all paper copyrights are owned by the author. The rest copyright 2003-2005 TechTarget

Privacy : Contact