Creating your first project
oak9 automatically collects and analyzes infrastructure code that for any vulnerabilities before you deploy. Creating your project is the first step.
Projects are an application or workload that you want to secure in the cloud.
In modern cloud native architectures there are hundreds of cloud native features and services that are interacting with each other via access policies, events, network communications, etc. These services are often developed by different teams or business units each with their own life cycles. This makes it very difficult to infer boundaries of an application or workload. A project is a flexible way for an organization to help define these often-blurred boundaries and enable oak9 to dynamically apply specific security requirements and standards that the organization is looking to meet.
That said, creating a project is simple - it only takes answering 5 questions.
Hit the big '+ New Project' button in your top menu. Give it a name and answer 5 questions.
Tell us how you application architecture is built and deployed
- Public cloud (i.e. Aws, Azure)
- Deploying to a public cloud environment means the infrastructure and services being utilized are shared broadly
- Private cloud (i.e. on prem or data centers)
- Deploying to a private cloud environment means the infrastructure and services being utilized are not shared outside the organization.
- Hybrid - split across the public cloud and data centers
- These application components are being deployed across a combination of public, private, or on-premise environments.
Data sensitivity relates to the extent to which access to data should be limited and the potential risk associated with unauthorized access to data. Data can be classified along a spectrum from public to business sensitive.
Public data is any information that is in the public domain, the unauthorized access to which poses little or no risk. At the other end of the spectrum is business sensitive data, or data that must be strictly protected from access by outside and/or unauthorized parties. An example of sensitive data is Personally Identifiable Information, or PII. PII data permits the identity of an individual to be directly or indirectly discovered and includes home address, social security number, financial or medical records.
Business sensitive data includes intellectual property, trade secrets, and financial and customer data. If the project created must conform to data protection standards or regulations such as HIPPA, PCI-DSS, or GDPR, refer to those standards to discern the level of sensitivity, and therefore data protection, that must be configured into the project.
As noted, the level of data sensitivity can be chosen for the project by referring to the data protection standard to which the project must conform. Choose public if the data is generally available in the public domain. Choose business sensitive if access to the data must be strictly limited to authorized users, or categories of authorized users. Choose a setting between those two points depending upon the extent to which access to the data should be limited.
Business Impact addresses the Impact that a loss/incident could have on your organization
- The Impact can be financial loss, disruption to business operations or systems, legal, regulatory, reputational, or related to safety
- Select the business impact that would apply if the confidentiality of the platform is compromised_._
High: Catastrophic or significant impact to the business
Medium: Moderate impact to the business
Low: Low impact to the business
Only one impact level can be selected for a project
End Users addresses the type of users that will be interacting with the oak9 platform
- Select the type(s) of end-users.
- Business Partners
Select all end-user types that apply
oak9 incorporates your compliance and regulatory requirements to provide security design guidance for your application. We have out-of-the box support for a number of industry standards, compliance frameworks and regulatory requirements that you want your application to adhere to.
Selecting your compliance frameworks is an important step in ensuring that oak9 understands the business context of your application. If your organization provides services within a unique regulatory environment, this will drive unique security requirements that oak9 will ensure your application addresses. Some compliance frameworks have different levels of rigor (e.g., NIST SP 800-53 has High, Medium and Low levels; HITRUST has increasing levels of rigor from 1-3). oak9 will ensure that your application architecture aligns with the security requirements of a given industry standard or compliance framework to satisfy the level of security rigor required.
Another advantage of selecting the applicable compliance frameworks is that oak9 will provide visibility into how your application architecture is fulfilling your compliance frameworks. Design gaps will be mapped to selected compliance frameworks along with oak9’s technical security requirements. Oak9 can generate reports for auditors and compliance professionals to provide real time compliance and security information about your application.
Selecting “Not Sure” under compliance frameworks will skip the validation of regulation-specific requirements but will still assess for design gaps and validate security best practices. You can add or change the compliance frameworks at any time by going to your project’s page and clicking the edit button near compliance frameworks.