Data Access Control and Authentication

---

Data Access Control in UniAPT:

1. Role-Based Access Control (RBAC):

   • Implementation: UniAPT uses RBAC to define access rights based on roles within the organization. Roles such as administrators, developers, and analysts have distinct access privileges.

   • Application: This method is particularly useful in managing access to different segments of the database, ensuring that employees can access only the data necessary for their role.

2. Attribute-Based Access Control (ABAC):

   • Implementation: ABAC in UniAPT involves defining access permissions based on a combination of attributes like department, job function, and project involvement.

   • Application: Useful for complex environments where access needs are dynamic and can change based on project requirements.

3. Mandatory Access Control (MAC):

   • Implementation: Used in highly sensitive parts of the project, MAC restricts access based on predefined security classifications.

   • Application: Essential for protecting top-secret or confidential data, often used in conjunction with security clearance levels.

4. Discretionary Access Control (DAC):

   • Implementation: Data owners in UniAPT have the discretion to grant access to their data. This method offers flexibility but requires stringent oversight.

   • Application: Common in collaborative environments where project leads need to control access to their data.

5. Temporal Access Control:

   • Implementation: Access permissions are time-bound, aligning with contract durations or specific project timelines.

   • Application: Ideal for granting temporary access to contractors or interns.

Authentication Methods in UniAPT:

1. Password-Based Authentication:

   • Used as the primary authentication method for both employees and end-users. Enhanced by enforcing strong password policies.

2. Two-Factor Authentication (2FA):

   • Implemented as an additional security layer, requiring users to provide two forms of identification.

   • Typically combines a password with a one-time code sent to a user’s phone or email.

3. Biometric Authentication:

   • Used for high-security areas, involving fingerprint or facial recognition technologies.

   • Ensures that access is granted only to verified personnel, reducing the risk of unauthorized access.

4. Token-Based Authentication:

   • Employees and users may be provided with physical or digital tokens that generate time-sensitive codes for authentication.

   • Commonly used for accessing critical systems within UniAPT’s infrastructure.

5. Certificate-Based Authentication:

   • Involves digital certificates for authenticating users, particularly in secure communication channels.

   • Ensures the identity of users and the integrity of the data being transmitted.

6. Single Sign-On (SSO):

   • Streamlines the user experience by allowing employees and users to access multiple applications with a single set of credentials.

   • Reduces password fatigue and improves compliance with security policies.

7. Behavioral Authentication:

   • Continuously monitors user behavior for anomalies.

   • Can detect and respond to unusual patterns that may indicate unauthorized access.

---

These access levels indicate the degree of database and system access granted to each category, from junior developer to lead developer.

---

Breakdown of Access Levels:

1. Junior Developer:

   • Access Level: 40%

   • This role, has limited access, focusing on certain areas of the project without access to more sensitive data.

2. Developer:

   • Access Level: 60%

   • Developers have more access than junior developers, including additional areas of the project, but still limited access to the most sensitive data.

3. Senior Developer:

   • Access Level: 80%

   • Senior developers, given their experience and responsibility, have access to most of the project, including some sensitive areas.

4. Lead Developer:

   • Access Level: 100%

   • Lead developers have full access, reflecting their high level of responsibility and the need to control all aspects of the project.