Recent orders
Database Security for 21st century business
Database Security for 21st century business
Introduction
Most companies have servers for different purposes; however, the most critical servers any company has is the database servers. Data such as client details, financials, and human capital are the data that support any business in operations. For this reason, there is an increasing concern about the general protection of databases. Any breach of security would lead to either loss of data, exposure of sensitive data, unauthorized access to sensitive information or access to classified files. As companies develop, so is the need to secure the data stored within the databases. The benefits of controlled, protected access to the classified files as well as the preservation of the general integrity, standards and consistency of these data is much more expensive (Shamimabi, & Nicholas, 2008).
The concept of database security is much more focused on the, physical security, network security, encryption and authentication. The main constructs that the concept of database security thrives on includes confidentiality or protection from informal disclosure, integrity or prevention from illegal data access, and availability of equipment for identifying and recovering errors that might cause a denial of access to information. In the process of ensuring that the data stored are secure, most companies try to restrict access using software, reduce vulnerability, eliminate interference as well as upgrade their database auditing mechanisms.
Database security problems
Physical Commuters are becoming physically accessible to unauthorized users
Personnel Organizations are becoming more involved in system administration and database security
Procedural Most organizations have same people manage various operation of the database. This exposes the organization and its data to various risks, which necessitates the need for background checks.
Technical Storage, manipulation, and transmission of the data stored in the database. This needs safeguarding by technology that can enforce particular information control policies.
Database securities current and future trends
Database has undergone a number of metamorphoses; the main metamorphosis is the security lay out. Amongst these is the activity monitoring and blocking, classification, Encryption, consolidation, and configuration. However, organization can achieve these using various software. In this light, most companies dealing within database security have tried to developed software and application, but the most effective one is the product of oracle. it has solution for activity monitoring and blocking protection of databases irrespective of the platform is important, however, it should also be cost effective. Most companies use firewalls for windows based databases forgetting the vulnerability of their databases if open source software are used to hack into these databases (Shamimabi, & Nicholas, 2008).
The activities of the database on any network need monitoring to prevent any form of unauthorized access. Oracles have achieved this by preventing SQL injection and role escalations. Any database security system must prevent these in real time. The SQL grammar technology is an effective platform for reducing millions of SQL statement to few SQL characteristics. It has a high level of accuracy, performance and flexibility (Sandhu, 2008).
The system should be able to enforce white; lists and blacklists (positive and negative security model to provide protection without costly false positives. It should be able to allow for addressing SOX, PCI, HIPAA/HITECH, any other regulatory requirement. This should be easy to achieve without necessarily changing the existing databases.
Privileged User and Multi-Factor Access Control:
The cost of protecting corporate data should not be hefty therefore; organization should seek ways of protecting their data cheaply. The most trusted is the Oracle Database Vault; oracle database vault is an effective way by which organization can address regulatory directives. Organization also needs to secure their existing application, as is a mandatory requirement by some regulation of which Gramm-Leach-Bliley Act (GLBA) is the key. They call for separation of the duties from the any other activities related to data management with the aim of securing data and make certain that the veracity of data is managed. Organization face increased challenge of proactively safeguarding of their application data kept in their databases. In this way, organization will use data for the intended purpose and not adversely. Only Privileged database clients should only access data. This requires the need for multifactor policy within the organization that can control the level of access by use of any built in factor. This may include instance, IP address, application record, application bypasses as well as the authentification methods.
Data Classification:
Shamimabi, & Nicholas, (2005), argue that industry leading application software is important. The bottom line of any database security is to classify data effectively in order to mediate access to organization data stored within the databases irrespective of the classification. A good database security system should be seamless to meet all the level of security. Organizations specifically design these systems to meet the requirement of the multilevel security requirements. Organization need systems that can classify data to allow access based on need to know. In this way, organization can protect the privacy of their data and realize the regulatory compliances. Label security should be integrated with identity management to enable centralized definition of the organization policy. The database systems should be able to support parent Data Encryption and offer hold up for PKI, Kerberos, and any other RADIUS-based well-built validation systems.
Sandhu, (2008), argues that database security should be cost effective and comply with various privacy and regulatory requirement such as the Sarbanes-Oxley, or the Payment Card Industry (PCI) and even the latest Data Security Standard (DSS). However, the Health Insurance Portability and Accountability Act (HIPAA), is a new regulatory mandate, which might require constant upgrading necessitating the need for flexibility and compatibility of systems. Customers should be able to transparently encrypt any of their application data and other sensitive columns like their credit card numbers social security and PIN numbers while in the database as well as in back up devices or even over then networks. The systems need to be cost effective.
Consolidated Auditing And Reporting:
There are many insider threats that most organizations phase. However, databases security systems need to automatically collect and consolidate the audits that the organization carries out in search of quality and total security. Organization are in need of systems that offer them secure and scalable audit warehouses that also enable simplified recording and automating the collection and final consolidation of audit data. Organization need to control database audit centrally and managed from within the database security system to reduce the cost related to IT security.
Secure Configuration Management,
According to Baker, et al, (2009), organization should be ready to increase the level of the database security and compliance with the IT control frameworks. This includes frameworks like Control Objectives for Information and related Technology: (COBIT), global directives require internal control, database security configuration management global directives. It should enhance discovery, and vulnerability scanning while ensuring compliance benchmarking, including any other functionality such as central management of database configuration. Organizations require this to detect and prevent configuration drift in the databases. Organizations should also have systems that can alert them in case of critical patches issued by various security framework developers. This, might help in invoking a patch wizard that automatically deploys patches and ensure that application databases within organizations are always updated and secure from unauthorized access (Bertino, Byun, & Kamra, 2007)..
Data Masking
There is increasing need for marking of sensitive information by replacing them realistic values. In this way, organization can use production data for the purpose of analysis, development, and even sharing with the out-sourced partners. Organization can also share these data with offshore partners as well. This might apply the use of templates readily available in libraries and the format rules. This consistently transforms data with the view of maintaining referential integrity for all application used within the organization.
Conclusion
While protecting the database from intrusion is important, it is also important to underscore the need for management restrain and controlled access. This will go a long way in ensuring that the company has the best protection from espionage, hacking, data leaks and data theft. The main database protraction platforms include oracle.
References
Baker, H., Hutton, A., Hylender, D., Novak, C., Porter, C., Sartin, B., Tippett, P., & Valentine, (2009). The 2009 data breach investigations report. Verizon Business. Retrieved January 31, 2010,
Bertino, E., Byun, J., & Kamra, A. (2007). Database security. security, privacy, and trust in modern data management (Data-centric systems and applications) (pp. 87-102).New York: Springer-Verlag.
Sandhu R., (2009). Database security concepts, approaches, and challenges: IEEE Dependable secure computing
Shamimabi P., & Nicholas R., (2008).Protocol engineering for web service conversations: journal of Engineering Applications of Artificial Intelligence, Special Issue on Agent-oriented Software Development
Database management systems
Database management systems
Name
Professor
Institution
Course
Date
Database management systems
Q#1)What are the advantages and disadvantages of implementing distributed and centralized databases? Does the size and location of the organization dictate if the database is centralized or distributed? Why?
Distributed database is a collection of data which are connected in a system through a simple logical network. They are managed through a distributed database management system in a single network. In the system, each part has its own dat6abse and an operating system. On the other Hand, a centralized database management has all the data stored in a single place fined as collection of logically distributed database which are connected with each other through a network.
The advantages of a centralized database are that all the data can be mined from the same network, this enhance the efficiency of the system and data recovery. This is also advantageous as the systems can be maintained from a central place in well contained manner. Centralized database is limited to those at central place, any downtime in the system leads to lose as the system is completely locked down
The distributed database is advantageous because the data can be accesses by geographically distributed clients without slowing down the system. This system is also advantageous because of the location transparency (Korth, & Silberschatz, 1998).
The size and location of the organization does not determine if the database is distributed because distribution of the database depends on the storage facilities and the computers in use. In a distributed system the remote databases have their own local autonomies over their data as they can take responsibility for the security of the data, the backup and recovery. They also control the concurrency of the database as well.
Q#2) what are some of the important considerations regarding DBMS/Database design? Explain why these considerations are important.
1) Security – DBMS is a very important part of any setting that takes care of the data stored in the database, security of the system should be given the highest priority. This does NOT only apply to the data in the data base but also to the [possible breaches. Therefore security of the dbms also concerns the hardware, software, people, and data. THIS requires the implementation of a superior mission objectives for the whole debase management systems. This increasing interest in the security of then database is as results of the reliance on the computer for the storage of data. The main concepts in ensuring the security of a DBMS include authorization, Views, backup and recovery, integrity, encryption and RAID (Elmasri, &Navathe, 2004).
2) Transaction rate: the kind of traffics to the data base. A debase is supposed to be scalable to allow for future un-predetermined database accesses. This will ensure that the number of systems downtimes is reduced and the throughput is increased thereby enabling the organization to realize their database design objectives. The designer should know whether the system is read only or both. Determination of the usage patterns also helps in determining if the system can work at peak times or even if the usage patterns are evenly distributed
3) The nature of the uptime- uptimes is also another important factor to consider as it determines the number of downtimes s set is supposed to register to [prepare for the possibilities of failures. The uptimes range from the normal 16×5 and the 24×7. But it is imperative to know that the 24×7 does not allow for downtimes when then systems can be maintained
4) The nature of database administration- according to Elmasri, &Navathe, (2004), it is important to consider the way the database will be administered, as it helps in reducing the number of system downtimes when administering the database. If the administration is to be carried every day at a central point or if the administrations to be carried at different remote points. DB administration may include backups, transfers to other systems, systems integrations, data loading etc are much more important to consider especially if the database is used for commercial purposes (Korth, &Silberschatz, 1998).
Q#3) Does MS Access support all nine DBMS functions identified listed in chapter service? Why or Why not? Describe how MS Access implements these functions.
Teorey, Lightsome &, Nadeau, (2006), states that the main functions of database management systems are: indexing, Views, Security, Integrity, Concurrency, Backup/Recovery, Design, Documentation and Update/Query. Ms Access can support a number of this function, but cannot support some functions due to incompatibility between the systems. For example, access has a number of query performance problems based on the resource mamanement systems used in the latest version of the databases. This was dues to the incompatibility and causes delays in returning the delays. However, Ms Access uses the hot fixes KB2553029 to speed up the query performance. On the other hand, ms access does not function in a number of operating systems like the Mac Os, Linux, BSD, and Amiga etc. this is due to the configuration systems used in the systems (Raghu, & Gehrke, 2000).
There are a number of functionalities such as connectivity and interactions that the ms access does not support. The ms access is a native PHP; it is therefore not easy for their connectivity to offer high indexing functionality and query / update. Ms can only achieve this by using the open database management system for direct access. Then reason form thins is that ms Access is a low end natively DBMS with a poor middle-tier PHP script. Ms can also reverse engineer the script to work sufficiently.
Ms Access has a limited support for the storage functionality. This is achieved but importing database for Ms Access jet 4. By conecting ms access to live databases through the ODBC, one can easily imports the database schemas into any standard UML model. This also enhances the level of synchronization between the data models and the live databases (Teorey, Lightsome, & Nadeau, 2006).
References
Elmasri, R. Navathe, S. (2004). Fundamentals of Database Systems. 4th ed., Pearson Addison Wesley,
Korth, H.; Silberschatz. (1998). Database Systems. Third Edition. Makron Books.
Raghu R., & J. Gehrke., (2000). Database Management Systems, Second Edition, McGraw-Hill,
Teorey, T.J., Lighstone S., Nadeau, (2006). Database Modeling and Design, 4th. ed., Morgan Kaufmann Publishers, Inc, San Francisco
Database Design Database Architecture
Database Design: Database Architecture
A database is defined as an organized collection of data. Today most Database Management Systems use different database system architectures such as centralized and client-server systems, server system architectures, parallel systems, distributed systems and many others for system implementation. However, in this case, the database architecture being used for my subsystem is a three-level architecture that has external level, internal level and conceptual level (Hellerstein, Stonebraker & Hamilton, 2007).
In physical database, the users’ view of the data is defined. My subsystem is a customer relationship system (CRM) where customers interact with the system to purchase goods online. Conversely, the managers also interact with the system to manage the employees (Hopper, 2008). The following is an entity-relationship diagram (ERDs) of the subsystem for CRM. In the diagram;
Manager manages Employees
Manager manages Customers
Manager control Goods
Customer orders goods from website
Customer signs up in a website
5172710192405Goods name
Goods name
17081513970Employee name name
Employee name name
-914400170180Employee ID no.
Employee ID no.
1028700169545Managers ID no.
Managers ID no.
2723515163195Managers Name
Managers Name
3676650150495Controls
Controls
5229225215900Goods
Goods
646430215900Manages
Manages
-590550255270Employees
Employees
21443958255Manager
Manager
546735087630Goods no.
Goods no.
1885950200025Customer ID
No.
Customer ID
No.
715010200025Customers
Customers
3781425120015Warehouse
Warehouse
-208915103505Custome Name
Custome Name
The below diagram is a use case Diagram representation for the subsystem to be implemented. Use case diagram is the view of system that looks on the behavior of the system as it appears to external viewers.
Database architecture is essential for system implementation in that it maintains a catalogue of schemas, users as well as, applications. Database architecture also allow for the storage, retrieval along with the manipulation of data. The other significance include; authorization and security, integrity and consistency services as well as, promotion of Data interdependence (Connelly, 2001).
References
HYPERLINK “http://www.bibme.org/” o “Edit this item” Connelly, J. (2001). Architecture Database on DIALOG: a user’s manual. London: British Architectural Library, Royal Institute of British Architects.
HYPERLINK “http://www.bibme.org/” o “Edit this item” Hellerstein, J. M., Stonebraker, M., & Hamilton, J. (2007). Architecture of a database system. London: Now.
HYPERLINK “http://www.bibme.org/” o “Edit this item” Hopper, T. (2008). Distributed relational database architecture: connectivity guide (4th ed.). New York: Prentice Hall PTR.
