Week 4 Assignment DS

%87

%3

SafeAssign Originality Report Database Security - 201950 - CRN165 - Rucker • Week 4 Paper

%90Total Score: High riskVenkatesh Bodhupally Submission UUID: 60a7fe0d-70d5-81ac-a8fd-c599f4d1d3ea

Total Number of Reports

1 Highest Match

90 % Users and Roles in Database - Venkatesh.doc

Average Match

90 % Submitted on

07/25/19 04:17 PM EDT

Average Word Count

720 Highest: Users and Roles in Database - Venkat…

%90Attachment 1

Institutional database (4)

Student paper Student paper Student paper

Student paper

Global database (1)

Student paper

Top sources (3)

Excluded sources (0)

View Originality Report - Old Design

Word Count: 720 Users and Roles in Database - Venkatesh.doc

2 5 1

3

4

2 Student paper 5 Student paper 4 Student paper

Source Matches (15)

Student paper 100%

Student paper 100%

Student paper 100%

Student paper 82%

Student paper 87%

Running Head: USERS AND ROLES IN DATABASES

1

USERS AND ROLES IN DATABASES

3

The Relationship between Users and Roles in Databases

Venkatesh Bodhupally

The Relationship between Users and Roles in Databases

For any association, databases are referred as the gemstones for the users of valued, private and sensitive business data. Running businesses are ordered to supply timely and precise data, so as protect them too. Security provides an integral competitive verge for every prominently working database. Hence, database givers are needed to prioritize

the data guidance to acquire loyal clients who can acquire faith in the system built to protect valuable data effect effectively, (Soniya, 2018). Various ways are used but database users, according to their privileges and roles. Users are generally categorised into three groups: Superuser- often he/she will be the database administrator and they will be creating them automatically and the moment one creates a new database. Superusers can conduct all database procedures, in addition to cancelling the other users and roles privileges. However, the superuser does not have all the permissions as the Linux superuser. Object owner- such a user can generate certain objects in database, same like a table or view. It is default that only a superuser or owner can act on a database object. All others, all object owners and non-superusers are PUBLIC users. “Such users are given a PUBLIC role. Object owners are taken as public users for objects they do not possess (Settles, 2016)”. On the other side, roles can be defined as a group of privileges. Privileges are a kind of permission that allows the user to perform a command on a database object. In addition, permissions can be assigned to or rescinded from users or roles. Therefore, a role can be a group, database user or both. “Database objects can be owned by roles and can allocate privileges on those objects to other roles to govern entrée to the objects Muller, 2017”. In addition, roles can be affiliates of additional roles; therefore a member role can take over object privileges of its original role. When roles are used, manual assigned sets of privileges user by user is avoided, that is, numerous users might be granted the “administrator” role. Roles can also be used to sustain consistency. For instance, when granting multiple privileges to users separately, one can forget to grant a role, this can be prevented when roles are used (Settles, 2016). There are a few reasons why jobs are utilized as opposed to simply appointing rights and benefits to each individual client. Job based authorizations serve to include an additional layer of arrangement what's more of what is allowed by client based affirmation. Clients are still offered with a login just as password, in any case, rather than their affirmation being administered on a different point, job established access empowers it for administrators to be dispensed to accumulations that are along these lines allotted explicit capacities, (Soniya, 2018). Such normal gatherings incorporate chairmen, super clients or directors. The upsides of this methodology are that it is far more settled to oversee client capacities in mass since modifying assents of a particular job will adjust the designs for all administrators designated that part. “Along these lines jobs are anything but difficult to change, for example, including a page and choosing no one but administrators can get to it is simpler as changing the administrator job (Soniya, 2018)”.

When taking care of new workers and employment changes the accompanying ought to be put into thought; one should just allow benefits to clients who need such benefit to achieve their obligations. Allowing pointlessly inordinate benefits to another representative can bargain security. Since framework benefits are ground-breaking, databases of course are designed to deflect non-authoritative clients from playing out any framework benefits (Soniya, 2018). Reference

Muller, L., Wasser, M. M., & Maestro, A. A. (2017). U.S. Patent No. 9,852,206. Washington, DC: U.S. Patent and Trademark Office. Retrieved from

https://www.uspto.gov/sites/default/files/documents/fy18pbr.pdf

Settles, C. (2016, March 18). Role-based Access vs. User-based Access. Retrieved from https://technologyadvice.com/blog/information-technology/role-based-access-vs-

user-based-access/ Soniya. (2018, August 24). Understanding Users, Privileges, and Roles. Retrieved from https://www.vertica.com/blog/understanding-users-privileges-roles/

1

1

2

2

2

3 4

2 5

2

1

Student paper

USERS AND ROLES IN DATABASES

Original source

Users and Roles in databases

1

Student paper

USERS AND ROLES IN DATABASES

Original source

Users and Roles in databases

2

Student paper

The Relationship between Users and Roles in Databases

Original source

The Relationship between Users and Roles in Databases

2

Student paper

The Relationship between Users and Roles in Databases For any association, databases are referred as the gemstones for the users of valued, private and sensitive business data. Running businesses are ordered to supply timely and precise data, so as protect them too.

Original source

The Relationship between Users and Roles in Databases For any organization, databases are the gemstones for repositories of very sensitive, private, and valued business data Thriving businesses are mandated to supply precise and timely data, in addition, to protect them as well

2

Student paper

Hence, database givers are needed to prioritize the data guidance to acquire loyal clients who can acquire faith in the system built to protect valuable data effect effectively, (Soniya, 2018). Various ways are used but database users, according to their privileges and roles. Users are generally categorised into three groups: Superuser- often he/she will be the database administrator and they will be creating them automatically and the moment one creates a new database.

Original source

Therefore, database providers are required to prioritize data protection so as to acquire loyal customers who can have faith in the system established to effectively protect valuable data (Soniya, 2018) Various ways are used but database users, according to their privileges and roles Users are generally categorised into three groups Superuser- often he/she is the database administrator and is created automatically the moment one creates a new database

Student paper 88%

Student paper 92%

Student paper 93%

Student paper 98%

Student paper 88%

Student paper 100%

Student paper 85%

Student paper 100%

Student paper 96%

Student paper 100%

2

Student paper

Superusers can conduct all database procedures, in addition to cancelling the other users and roles privileges. However, the superuser does not have all the permissions as the Linux superuser. Object owner- such a user can generate certain objects in database, same like a table or view. It is default that only a superuser or owner can act on a database object.

Original source

Superusers can conduct all database procedures, in addition to cancelling privileges to other users and roles However, the superuser does not possess all the privileges as the Linux superuser Object owner- such a user can generate certain database objects, such as table or view By default, only a superuser or owner can act on a database object

2

Student paper

All others, all object owners and non- superusers are PUBLIC users. “Such users are given a PUBLIC role. Object owners are taken as public users for objects they do not possess (Settles, 2016)”. On the other side, roles can be defined as a group of privileges.

Original source

Everyone else- all object owners and non- superusers are PUBLIC users Such users are given a PUBLIC role Object owners are taken as public users for objects they do not possess (Settles, 2016) On the other hand, roles can be defined as a group of privileges

2

Student paper

Privileges are a kind of permission that allows the user to perform a command on a database object. In addition, permissions can be assigned to or rescinded from users or roles. Therefore, a role can be a group, database user or both. “Database objects can be owned by roles and can allocate privileges on those objects to other roles to govern entrée to the objects Muller, 2017”.

Original source

Privileges are a kind of permission that allows the user to perform a command on a database object In addition, privileges can be granted to or rescinded from users or roles Therefore, a role can be a group, database user or both Database objects can be owned by roles and can allocate privileges on those objects to other roles to govern entrée to the objects

2

Student paper

In addition, roles can be affiliates of additional roles; therefore a member role can take over object privileges of its original role. When roles are used, manual assigned sets of privileges user by user is avoided, that is, numerous users might be granted the “administrator” role. Roles can also be used to sustain consistency.

Original source

In addition, roles can be affiliates of additional roles therefore a member role can take over object privileges of its original role When roles are used, manual grant sets of privileges user by user is avoided, that is, numerous users might be granted the “administrator” role Roles can also be used to sustain consistency

2

Student paper

For instance, when granting multiple privileges to users separately, one can forget to grant a role, this can be prevented when roles are used (Settles, 2016).

Original source

For instance, when granting multiple privileges to users separately, one can forget to assign a role, this can be prevented when roles are used

3

Student paper

Patent and Trademark Office.

Original source

Patent and Trademark Office

4

Student paper

Retrieved from https://www.uspto.gov/sites/default/files/docu ments/fy18pbr.pdf

Original source

Retrieved November 1, 2017, from https://www.uspto.gov/sites/default/files/docu ments/fy18pbr.pdf USAJOBS

2

Student paper

(2016, March 18). Role-based Access vs. User- based Access.

Original source

(2016, March 18) Role-based Access vs User- based Access

5

Student paper

Retrieved from https://technologyadvice.com/blog/informatio n-technology/role-based-access-vs-user- based-access/ Soniya.

Original source

Retrieved from https://technologyadvice.com/blog/informatio n-technology/role-based-access-vs-user- based-access/

2

Student paper

(2018, August 24). Understanding Users, Privileges, and Roles. Retrieved from https://www.vertica.com/blog/understanding- users-privileges-roles/

Original source

(2018, August 24) Understanding Users, Privileges, and Roles Retrieved from https://www.vertica.com/blog/understanding- users-privileges-roles/