Skip to main content

Security Docs

As a CNC Security SPOC, we should be aware of the documents which help in understanding the threat landscape for the CNC product portfolio. These documents include: 

  • Documents which help to understand the threat landscape presented by Cloud Native Environments - topics include security best practices and common threats associated with the CNC technologies: Kubernetes, Containers, Microservices, Containerized Software Delivery, infrastructure security, network security, MySql, etc. 
  • Documents which help to understand the threat landscape presented by 5G Core Networks - topics include security best practices and recognized 5G threats. 

Key:  

CNEMySQL5GInfrastructure
Date
Author
Document
Abstract
Keywords

 

OracleOracle Linux 7 Security GuideThe Oracle Linux 7 Security Guide provides a broad set of security guidelines for the Oracle Linux 7 operating system. The document details procedures, tools, and best practices for securing an OL7 based system.Audit, SSH, SCAP, Infrastructure

 

NIST

Application Container Security Standards

An early take on application container security standards from T-Mobile. The document describes the thread landscape and documents best practices for securing containerized environments.Docker, Repository, CNE

 

Center For Internet Security (CIS)CIS Oracle Linux 7 BenchmarkThe CIS Linux Benchmark - a set of best practices for hardening the Oracle Linux 7 Environment.Infrastructure
 
Center For Internet Security (CIS)The CIS Docker Benchmark - a set of best practices for hardening a Docker deployment.Docker, Containers, CNE
 
Center For Internet Security (CIS)CIS Kubernetes Benchmark

CIS Kubernetes Benchmark - a set of best practices for hardening a Kubernetes environment.

Kubernetes, Containers, CNE

 

HPThe HP iLO Security Guide provides a set of procedures and recommendations for securing the HP Integrated Lights-Out system management interface.Bare Metal, Infrastructure

 

Red HatThe Red Hat Linux Hardening Guidelines provides a set of procedures and recommendations for hardening Linux systems deployed in the T-Mobile environment.Infrastructure

29 Aug 2020

World Bank5G Security Threat ModelingNew technology components in a 5G network and the new services it provides and comprehensively analyze the risks in this ecosystem through a threat model the World Bank Group developed and to discuss the mitigating controls.5G, Threat Modelling

 

CNCFIn 2018, the Center for Cloud Native Computing Foundation sponsored an open-source audit of the security of Kubernetes. These documents provide highlights and recommendations. While most of these recommendations are targeted to the K8s development teams, some recommendations for securing deployments are also provided.Kubernetes, CNE

 

NISTNIST SP 800-204 documents Security Strategies for Microservice-based Application Systems. These strategies focus on the best practices for architecture and design of containerized microservices.Microservices, Containers, Design Best Practices

 

Center For Internet Security (CIS)CIS MySQL Benchmarks - a set of best practices for securing MySQL.MySQL, Best Practices

 

OracleThe Oracle MySQL Security Best Practices provides a set of recommendations for securing MySQL databases. The paper documents common attack vectors and makes recommendations on how to prevent or mitigate these standard attacks.MySQL, Best Practices

 

MicrosoftKubernetes Attack MatrixMicrosoft's Kubernetes Attack Matrix provides a threat catalog documenting the typical ways the Kubernetes environments are attacked.Kubernetes, Threat Catalog

 

BTTelecoms Security FrameworkThe Telecoms Security Framework documents a set of Principles, Requirements, and Tests that are mandatory for all network operators providing service in the UK. The document documents requirements for management plane, signaling plane, as well as operational environments. Details on supply chain management and planned security audits is also covered.Telecom, 5G, 4G, Threat Catalog, Core Network Hardening

 

5G Americas5G and the CloudA broad overview of the 5G Design Architecture including historical overview of core network technology evolution.Telecom, 5G, CNE, NFV, CI/CD, Microservices, Service Based Architecture, Service Mesh

 

5G Americas5G Security WhitepaperAn overview of the Security related 5G standards; a discussion of perceived 5G Threats; a list of possible mitigationsTelecom, 5G, Threat Catalog, Threat Mitigation, 5G Security Standards

 

NIS Cooperation GroupEU Risk Assessment of 5G NetworksA robust assessment of 5G Network Security Risks. Describes threats and threat actors, assets being protected / attacked, common vulnerabilities for various stakeholders, and risk scenarios. A great source document for ARA authors.Telecom, 5G, Threat Catalog, Risk Assessment

 

European Telcom ProfessionalsTelcom Security LandscapeA short list of security threats and opportunities as identified by the ETIS group. A one page infographic.Telecom, 5G, Threat Landscape

 

NIS Cooperation GroupCybersecurity of 5G NetworksBuilding on the EU Risk assessment document (above), this document descibes a "toolbox" of possible mitigations which can be employed to protect the 5G core network. A great source document for ARA authors.Telecom, 5G, Threat Catalog, Risk Assessment

Comments

Popular posts from this blog

Supporting OpenTracing jaeger in spring boot applications

This page describes code changes in a typical spring-boot based application to support OpenTracing and jaeger. Instrumenting a tracer If you are creating a simple spring boot application that uses  spring-boot-starter-web , by default, the application does not support writing traces to jaeger. To support jaeger tracing, the first thing is to modify the build.gradle to add dependency of jaeger: dependencies {      implementation  'org.springframework.boot:spring-boot-starter-web'      implementation  'io.opentracing.contrib:opentracing-spring-web-starter:3.0.1'      // support opentracing jaeger      implementation  'io.opentracing.contrib:opentracing-spring-jaeger-starter:3.1.2'      testImplementation( 'org.springframework.boot:spring-boot-starter-test' ) {          exclude group:  'org.junit.vintage' , module:  'junit...

HOWTO on implementing scanning into a CI Pipeline

Introduction As a part of the Software Security Assurance guidelines, we are required to perform various types of security scanning.  Security scanning is a specialized kind of testing that attempts to identify potential software bugs that could make a deployed application vulnerable to attack and compromise.  As with any testing, the tests can be manual or automatic, and they wan be performed at various points in the development cycle.   We can classify security scanning into three general categories: Static Application Security Testing (SAST)   - performed against source code / configuration data a static scan looks for common logic errors that might lead to system compromise. Dy namic Application Security Testing  (DAST)  - Performed against a running system, a dynamic scan looks for vulnerable software / configurations that might lead to system compromise. Security Monitoring  - Deployed as a part of the system, a security monitor co...

Fortify Tooling User Guide

  Introduction The fortify-tools container is located within a shared repository in OCIR and requires a JWT to be able to access.  The variable WF_JWT will need to be set to a valid MAT You will want to choose one of three ways to use the Fortify SCA tooling: Integration Description Using the Fortify Tools Standalone to Scan a Project This is for using the tooling without integration in GitLab CI or Jenkins CI. Using the Fortify Tools In GitLab CI to Scan a Project This is for using the tooling against a project that whose code is hosted in GitLab and whose CI engine is GitLab CI. Using the Fortify Tools In Jenkins CI to Scan a Project This is for using the tooling against a project that whose code is hosted in GitLab and whose CI engine is Jenkins CI. Using the Fortify Tools Standalone to Scan a Project Simple Usage Run the Fortify Tools in a container docker run -t --rm -v <path to project source root directory>:/var/fortify/src phx.ocir.io/oraclegbudevcorp/cn-shared/s...