Scenario:

You are the security administrator at a saftware development company that handles projects of varying sensitivity$.$ The company employs a strict data integrify policy based on the Biba model. You have three project teams working on differeat projects classified at Public, Confidential, and Secret integrity levels

The development environment is structured as follows:

Team $1$ works at the Pablic integrity level.

Team $2$ works at the Ciafidential integrity level.

Teani $3$ works at the Secret integrity level.

The company uses an integrated developuent environment $($IDE$)$ software that enforces integrity controls. All teams use the same IDE for code development, which is configured to enforce the Biba model's principles.

Question:

You are tarked with conffipuring the access controls for a new shared code repository meant for collaborative development between the teams: Given the $"$No Write Up$"$ and $"$No Read Down" policies of the Bibal modet describe how you would set up the repository's access controls to ensure compliance with these rules. Address the following in your answer:

Which teams can sately share a repository without violating the Biba model's integrity rules?

If Team $2($Confidential$)$ needs to use a fianction developed by Team $1($Public$),$ what steps. mast be taken to incorporate that function into Team $2\text{'}$s prolect without compromising Integrity? integrity?