Build Place Security and Compliance¶
This page specifically covers security considerations for accessing environments and source code.
A Build Place environment is a short-lived IFS Cloud sandbox that Build Studio creates for your organization to build and validate customizations. It contains your customization code and IFS reference data. It must never contain your production or regulated data.
To keep validation simple, every Build Place environment comes with the same application and database accounts. As these accounts are shared across your organization, responsibility for managing the associated controls is shared between IFS and your organization.
Accounts in a Build Place environment¶
| Account | What it is for | Where you get it |
|---|---|---|
| IFSAPP (application user) | Signing in to the IFS Cloud application to validate customizations. It already holds the permission sets a validation needs, so you do not have to create users and grants in every sandbox. | Environment Card in Build Studio |
| IFSSYS (database user) | Direct database access from a developer IDE or Oracle client, over the VPN or *Teleport tunnel. | Environment Card in Build Studio under the Database Connection Details |
*Teleport is only applicable to FedRAMP and IFS Cloud Kaname Customers only.
Customizations are validated by running them as a user who already holds the permission sets the test needs. IFSAPP has that permission scheme by design. Creating individual users and permission sets in every short-lived sandbox would add work to each validation cycle and make results depend on how faithfully the grants were reproduced. The controls above, together with the absence of production data and the short life of each environment, are how IFS and you keep this arrangement accountable.
Note
Each Build Place environment gets its own passwords, generated when the environment is created and discarded when it is deleted. A password from one Build Place environment does not work on another.
Shared security responsibilities for Build Place¶
| Area | What IFS does | What you are responsible for |
|---|---|---|
| Access control | Shows credentials only to a person who has signed in to Build Studio with their own identity and has been granted access to that environment by your Build Studio administrator. | Deciding who may access Build Studio. Grant roles only to people who need them for customization work, and remove them when someone changes role or leaves. |
| Credentials | Creates each Build Place environment with freshly generated passwords for every IFS account in the database. | Handling credentials with care. Don’t store passwords in source repositories, tickets, chat messages or shared documents. Retrieve them from Build Studio when you need them. |
| Accountability and audit | Records of who created each environment and who retrieved its credentials are kept for specific period for audit purposes. | Treating shared credentials as your organization’s. Activity carried out with those credentials is attributed to the people who were issued them. Sharing them further inside your organization is your decision and your accountability. |
| Network access | Makes the database reachable only through a VPN or Teleport tunnel. The Teleport client signs you in with your own identity through Curity. The tunnel stays open for a limited period. | Keeping the VPN configuration file on a device your organization manages, and using it only when you need to connect to the environment. |
| Data | IFS does not input sensitive data in databases. | Keeping production and regulated data out. Use the test data IFS provides or synthetic data you create for the purpose. |
| Incident response | Provides new credentials with every new environment. | Reporting a suspected compromise. Delete the environment in Build Studio and raise a case with IFS Support. |
| Environment lifespan | Deletes the environment and every credential at the end of its lifespan or when a user deletes it. | Requesting only the lifespan you need. Extend an environment only while validation work continues. |
*Teleport is only applicable to FedRAMP and IFS Cloud Kaname Customers only.
The compliance level of the Build Place repositories¶
Every Build Place comes with two repositories: Customer Baseline, which holds the IFS Cloud release content your customizations build on, and Customer Solution, which holds your customization code.
In the IFS Cloud Commercial offering, these repositories are hosted in Azure DevOps.
In the IFS Cloud FedRAMP and Kaname offering, these repositories are hosted in GitHub Enterprise Cloud, in a dedicated GitHub organization that IFS creates for your Build Place in the United States region.
Note to FedRAMP Customers
The IFS Cloud FedRAMP offering is built to the FedRAMP Moderate baseline. The GitHub Enterprise Cloud, the source control system used for Build Place repositories, currently holds a FedRAMP Low (Class B) authorization rather than a Moderate authorization. GitHub has announced its intention to pursue a Moderate authorization. Until that authorization is granted, this component of the service operates at a lower authorization level than the rest of the offering.
IFS has selected GitHub Enterprise Cloud because it is the only FedRAMP-authorized source control service that supports the Build Place operating model for all customers, and because it stores customer code within the United States. IFS reviews this decision whenever GitHub’s authorization status changes, and as part of each annual assessment.
Your source repositories are the one part of Build Place where the certified level is Low. That is appropriate for what the repositories are meant to hold such as IFS Cloud customization source and configuration. It is not appropriate for sensitive data. Therefore, please keep the following out of your Build Place repositories:
- Controlled Unclassified Information, including Controlled Technical Information
- personal data about anyone
- production or business data from your IFS Cloud environments
- passwords, keys, tokens or connection strings
If customization work involves content of this kind, customers should consult their authorizing official before committing it and contact an IFS administrator. IFS will work with customers to identify a suitable alternative, so that such content is not stored in an inappropriate location.
How Access Works¶
Access to your repositories follows your Build Studio roles. When a Build Studio administrator in your organization grants someone a role, IFS creates a GitHub account for that person inside the IFS enterprise and adds them to the right team in your organization. The teams have fixed permissions: developers and technicians can push to Customer Solution and read Customer Baseline while administrators can manage both. When the role is removed, the access is revoked with it. People sign in through single sign-on, so there are no separate GitHub passwords to manage.
Changes to the Customer Solution Master branch need two approvals before they are merged. Your technicians and Customer Solution developers are notified as reviewers when a change is proposed.
Shared source control responsibilities for Build Place¶
Note
GitHub Organization is used for source control for FedRAMP and IFS Cloud Kaname customers, whereas Azure DevOps is used for IFS Cloud Commercial customers.
| Responsibility | IFS | User |
|---|---|---|
| Choosing and running the BP repositories, and tracking its FedRAMP status (Applicable to FedRAMP Customers only) | IFS | N/A |
| Creating your Azure DevOps/ GitHub repositories, keeping them private, and setting team permissions and branch policies | IFS | N/A |
| Creating and removing Azure DevOps/ GitHub user accounts when a Build Studio role is granted or revoked | IFS | You decide who in your organization gets a Build Studio role, and you remove people who leave |
| Signing in | IFS provides single sign-on through the identity provider configured for the offering | Your developers sign in with their own accounts; accounts are never shared |
What goes into customer-solution | IFS builds and delivers from it | You are responsible for the content, within the limits above |
What goes into customer-baseline | IFS maintains it | Read only |
| Copies of the repositories on the developers' computers | N/A | You handle them under your own policies |
| Audit trail of who has access and who did what in the repositories | IFS keeps the record of every role grant and revocation (visible to your administrators in Access Studio, and kept in IFS's logs) together with GitHub's audit log | You can ask us for evidence for your own authorization |