Three-tier architecture

client/server

browser/server

Balance of multiple control methods

Understand the boundaries between environmental controls and application controls

Balance of software functionality and security measures

Balance of functional requirements, security requirements and security mechanisms

usually inversely proportional to

Default installation does not guarantee security

Configuration security is not enabled (access should be denied by default)

Failure to follow the minimal installation principle

Post-patch installation

Clarify requirements and determine the basic safety objectives of the product

Risk analysis assessment, assessing threats and vulnerabilities, Estimate the cost/benefit ratio of different security countermeasures

Risk Management

Risk Analysis

Safety requirements

The project development and requirements management team conducts complex analysis of current and likely future functional requirements to ensure the new system meets end-user requirements

Project team members will also review the documents output during the initial phase of the project and revise and update them as needed.

For relatively small projects, the above processes are often included in the initial stages of the project.

Security requirements should also be formed accordingly. (Security requirements are determined during the requirements analysis phase, Security personnel must be involved during the requirements stage)

Software development as part of system design

Tools for describing user requirements and system internal behavior

design

security design approach

Questions to consider

The main work

Test type

Separation of environments and separation of responsibilities

verify (verification)

confirm (validation)

Focus on how to use and operate the developed system or application

Certification (Certification)

Appraisal or Approval (Accreditation)

Migrations and fixes

Correctly configure the security environment

Continuously conduct vulnerability testing, monitor system activity and audit events (A vulnerability is discovered during the maintenance phase and the action taken is to report)

If major changes occur, perform a risk assessment, and perform certification and accreditation processes (re-certification, re-accreditation)

Destroy data based on data sensitivity.

Destruction method

Management techniques that optimize design, manufacturing and support processes by integrating all necessary acquisition activities simultaneously using multi-discipline teams

IPPD facilitates meeting cost and performance targets from product concept to production, including on-site support

A key principle of IPPD is the multidisciplinary collaboration model of Integrated Product Teams (IPTs)

Representatives from all functional disciplines work with the Team Leader to build successful and balanced programs, identify and solve problems, and make sound and timely decisions

Team members may not necessarily contribute 100% of their time to the project, and a member may be on multiple IPT teams.

The purpose of IPTs is to make team decisions based on real-time input from all teams (e.g., project management, engineering, manufacturing, test, logic, financial management, procurement and contract management) including customers and suppliers

Team members for ITPs are composed of project manager-level members, including members from the enterprise and system/subsystem contractors

A typical IPT is at the program level and may, for example, consist of the following functional disciplines: design engineering, manufacturing, systems engineering, test and evaluation, subcontracting, quality assurance, training, finance, reliability, maintainability, support, procurement , contract management, suppliers and customers.

concept

in principle

Individuals and interactions over processes and tools Working software above thorough documentation Customer Cooperation Above Contract Negotiation Respond to change better than follow plan

Class defines the abstract characteristics of a thing

A class defines the properties of a thing and what it can do (its behavior)

The methods and properties of a class are called "members"

Object is an instance of a class.

The system allocates memory space to objects but not to classes; Classes are abstract. It is impossible for the system to allocate space to abstract things. Objects are concrete.

Attributes:

method:

The simplest understanding of encapsulation is packaging, which refers to hiding the properties and implementation details of an object. Only the interface is exposed to the outside world, that is, the internal state of the object is transparent to the outside world.

means hiding object information

public members

private member

Is a mechanism for creating one or more subtypes from an existing class.

Representation of logical relationships between data elements

scalar

linked list

hierarchical tree

cohesion

coupling

API is a connector for IoT (Internet of Things) that allows devices to connect to each other

Representational State Transfer (REST) ​​API

REST security expert usage advice

Three safe paths for REST APIs

response

Assemblies that manage and control data access

Organize and store data in a certain format, Record files that allow users to access, manage and update

Focus: Data collection, storage, recovery

Most concerned with integrity, followed by availability, and finally confidentiality

metadata

Features:

hierarchical database model

Network database model

relational database model

object-oriented database model

object-relational database model

Open Database Connectivity, ODBC

Object connection and embedding database, OLEDB

ActiveX Data Objects, ADO

Java Database Interconnect, JDBC

integrity (integrity)

polymerization (Aggregation)

reasoning (Inference)

deadlock (DeadLocking)

Other threats

Online Transaction Processing, OLTP

Online Analytical Processing, OLAP

Data warehousing and data mining

inference engine

knowledge base

timing

storage

vandalism

financial fraud

privileged access

Stealing transaction information

theft of intellectual property

denial of service attack

specific security

SAML

OAuth2.0

java applet

ActiveX control

Virus

worm

Botnet

Trojan horse

rootkit

logic bomb

characteristic detection method (signature)

Heuristic detection (heuristic) Abnormal behavior detected

Immunization program

behavior blocker

Antivirus program

Bayesian filtering

Features

Classification

Embed information security capabilities into federal information systems through the application of best practice management, operational, and technical security controls.

Maintain awareness of the security status of information systems through continuous strengthening of monitoring processes

Providing important information for senior leadership to drive decisions, including acceptance of risks to the organization's operations and risks to assets, individuals, other organizations, or countries arising from the use and operation of information systems;

Audit procedures assist in detecting any unusual activity

The audit level and audit type depend on the audit requirements of the installed software and the sensitivity of the data processed or stored by the system.

System resources should be protected when available

The need to establish a baseline

Performance of different servers and systems

Application functions and operation and maintenance issues

Effective intrusion detection

forensic analysis

Comply with various laws and regulations

The application compares or reconciles what is processed with what is expected to be processed

Compare totals

Check serial number

Check input accuracy: Data validation and validation checks should be integrated into appropriate applications

Character checks: Compare input characters to expected character types, such as numbers or letters

Range checks: Validate input data against the upper and lower bounds of the reservation

Relationship checks: Compare the input data to the data in the main record file

plausibility check (Reasonableness checks): Compare input data to expected standards, other forms of integrity checks

Transaction limits: Check the input data and compare it with the limits set by the management in the transaction.

Risk management is an ongoing process that spans the entire project life cycle

The risk management process includes risk planning, identification, analysis, monitoring and control

The identification of risks begins before the project is initiated, and the number of risks increases as the project matures.

Risk reduction steps can reduce the likelihood of an event occurring. Risk mitigation will incur costs and requires a cost-benefit analysis;

Continuity planning or a series of activities undertaken at or before an event occurs. Planning may be pre-emptive activities before a risk occurs or activities after a risk occurs.

Integrate into the SDLC process as well as the organization’s change management process

Use standardized risk assessment methods and report risks to stakeholders

Track and manage weaknesses identified during assessment, change management and ongoing monitoring

Basic Settings

Research

Assessment and testing

Mitigation ("rollback")

Deployment ("rollout")

Validation, reporting and logging

Implementing risk control measures requires testing

Code signing

Testing considerations

Regression Testing

acceptance test (Acceptance Test)

Obtain the identified requirements for software services or products, identify potential substitute software methods, and identify the risks of substitution.

Development requirements are included in the statement of work

Establish acquisition strategies and include identification of risks associated with various software acquisition strategies

Develop evaluation criteria and evaluation plan

Create/issue Request for Proposal (RFP) with description of work, offeror description, terms and conditions, pre-qualification and certification,

Evaluate proposals submitted by suppliers in response to Request for Proposal (RFP) or Invitation to Tender (ITT)

Complete contract negotiations including changes to terms and conditions

This stage is mainly about monitoring the supplier's work and accepting the final service or product delivery as agreed in the contract.

Establish and agree to contract work schedule

Implement change control procedures

Review and accept software deliverables

Sustainment (including risk management, assurance use case management and change management)

Disposal and offline

In subsequent phases, software risks must be managed through continuous assurance use case analysis and adjusted to reduce risk