mismatches in security weaknesses
The article, Layered, discusses security weakness within the frame of network architecture and how many “mismatch” or “overtax” the system. The author is trying to explain different variations of what might seem to be “normal” but is actually more of weakness when securing the system(s). (Mackey, 2002).
Mackey discusses many variations that could be a normal procedure for many organizations but “mismatches and overtaxed” are a common trait that can be overlooked. One example used in the article of “overtaxed” is the purchase a new database. This database could be a very sophisticated and could possibly store multitudes of confidential information and many organizations would not consider purchasing a separate server, due to cost-saving. This type of example could cost the organization money, in means of intrusion, as a separate server should be included with the new database. It was mentioned that by not using a separate server “if one database is compromised, others on that box are also at risk” (Mackey, 2002).
The basic information discussed in the article about mismatched and overtaxed, sounds pretty much like it states; mismatched is not “matching” the same “strengths” such as passwords (as I mentioned) and overtaxed is one “mechanism” handling multiple mechanisms – it’s just too much for one (over-doing it).
An example of overtaxed would be in regards to “shared-media networks”. It was stated in the article Trends in WAN Design, that many systems are being overtaxed because of the “network requirements” of “having to connect to remote sites; users to have remote access to their networks; growth of corporate intranets and increased use of enterprise servers (Cisco, N.d.)”. In order to prevent overtaxing, many are “turning to WAN technology”, along with multiple routers, as this will help with handling “critical information” and the protection of possible intrusion (Cisco, N.d.).
An example of mismatched I found in the article Software Engineering for Security: a Roadmap, discusses two different types of “framework” was the Unix System and COBRA platforms. The example “Unix systems and CORBA have different security policies and enforcement mechanisms” will cause an authentication problem. (Devanbu & Stubblebine, N.d.) “These difference greatly complicate systems where principals can authenticate themselves with either mechanism (Devanbu & Stubblebine, N.d)”.