artifact

Any document, record, or tangible item produced within a portfolio, program, or project that supports managing the work and communicates information to the team, stakeholders, and leadership.

Key Points

  • Exists at portfolio, program, and project levels across the entire life cycle.
  • Typical examples include charters, roadmaps, product backlogs, risk registers, reports, and dashboards.
  • Purpose is to enable decision making, track progress, and share information transparently.
  • Should have clear ownership, version control, and access management to remain accurate and useful.

Example

In an agile project, the team updates a sprint burndown chart each day. This artifact shows remaining work versus time, helping the team adjust their plan and giving stakeholders a clear view of progress.

PMP Example Question

Which option best describes an artifact in the context of portfolio, program, or project work?

  1. A meeting used to review progress and remove impediments
  2. A document or tangible item produced to support management and information sharing
  3. A change request approved by the change control board
  4. A role responsible for coordinating team activities

Correct Answer: B — a document or tangible item produced to support management and information sharing

Explanation: An artifact is a created item (e.g., plan, log, report) used to manage the work and communicate with stakeholders; it is not a meeting, role, or specific approval.

ICS/OT Cybersecurity Fundamentals — Security Built for Industrial Systems

Industrial control systems cannot be secured like ordinary IT. A forced reboot, aggressive scan, or incompatible patch can interrupt production and create real safety consequences. Effective OT security begins with understanding the systems, constraints, and risks unique to industrial environments.

This course gives IT professionals, engineers, operators, and security practitioners a practical foundation in ICS threats, zone and conduit design, risk assessment, passive asset visibility, and vendor evaluation. You will learn how IEC 62443, NIST CSF, and MITRE ATT&CK for ICS apply where availability and safety come first.

Eight reconstructed incidents—including Stuxnet, Triton, Ukraine 2015, Colonial Pipeline, and PIPEDREAM—show how attackers move through OT environments, what they target, and which defenses could have changed the outcome.

Watch the course preview, then build the vocabulary, frameworks, and judgment needed to take credible first steps in ICS/OT cybersecurity.

Explore the Course


ICS/OT Cybersecurity Fundamentals course preview

Build an ICS/OT cybersecurity foundation that fits the real environment

Standard IT controls can disrupt the industrial systems they are meant to protect. Learn how to assess OT risk, design zones and conduits, apply IEC 62443 security levels, use MITRE ATT&CK for ICS, and establish passive asset visibility without risking production. Eight reconstructed incidents connect attacker techniques to the controls that failed, giving you the vocabulary and judgment to make credible security decisions from day one.

Explore the Course