{
  "$schema": "https://ar-tik.com/data/schemas/course-record.schema.json",
  "generatedAt": "2026-07-02",
  "publisher": "Artik Lab s.r.l.",
  "canonicalDomain": "https://ar-tik.com",
  "course": {
    "id": "secure-ai-sdlc",
    "locale": "en",
    "language": "en",
    "family": "technical",
    "familyLabel": "Technical",
    "featured": false,
    "title": "Secure AI SDLC",
    "subtitle": "Practical corporate course for applying AI to secure AI software lifecycle, with exercises on realistic work, reusable materials and clear governance criteria.",
    "summary": "Practical corporate course for applying AI to secure AI software lifecycle, with exercises on realistic work, reusable materials and clear governance criteria.",
    "duration": "4-6 hours, customisable",
    "mode": "In-person or online lab, with guided exercises and materials adapted to the client.",
    "profile": "technical",
    "profileDescription": "For technical teams with programming and software architecture basics.",
    "problem": "Companies often approach secure AI software lifecycle through scattered experiments: a few prompts, a few enthusiastic users, many doubts about data, quality and responsibility. This course turns that uncertainty into an operating method. Participants work on realistic scenarios, learn where AI helps, where human review remains essential and how to make the practice repeatable inside the company.",
    "audience": "For technical teams with programming and software architecture basics.",
    "whenToChoose": "Choose this course when the company wants concrete progress on secure AI software lifecycle and needs training that produces usable workflows, not abstract theory.",
    "chooseIf": "When the company wants concrete progress on secure AI software lifecycle and needs training that produces usable workflows, not abstract theory.",
    "outcomes": [
      "Map the work and the decisions where AI can reduce friction.",
      "Build practical instructions, checklists and review criteria.",
      "Identify data, privacy and responsibility boundaries.",
      "Create reusable examples for the team.",
      "Define next steps for adoption and governance."
    ],
    "modules": [
      {
        "title": "Architecture and requirements",
        "description": "Goals, boundaries, data, services and risk assumptions."
      },
      {
        "title": "Build and integration patterns",
        "description": "Pipelines, interfaces, context, permissions and testing."
      },
      {
        "title": "Evaluation and quality",
        "description": "Metrics, review, regression tests and failure modes."
      },
      {
        "title": "Production and governance",
        "description": "Monitoring, security, audit, cost and maintenance."
      }
    ],
    "exercises": [
      "Map a realistic process connected to secure AI software lifecycle.",
      "Create AI-assisted outputs and review them critically.",
      "Define escalation and human review points.",
      "Build a reusable checklist for daily work."
    ],
    "materials": [
      "Operating canvas for secure AI software lifecycle.",
      "Prompt and instruction templates.",
      "Quality and privacy checklist.",
      "Risk/control matrix.",
      "Adoption notes for the team."
    ],
    "privacy": "The course uses synthetic, public, anonymised or client-approved materials. It explains how to minimise data exposure, protect confidential information, verify outputs and keep human responsibility explicit.",
    "prerequisites": "Basic technical familiarity with software, data or system architecture is recommended.",
    "faqs": [
      {
        "question": "Is the course tool-specific?",
        "answer": "No. Patterns and workflows are adapted to the tools and policies chosen with the client."
      },
      {
        "question": "Can company data be used?",
        "answer": "Only when accounts, contracts and internal policies allow it. Otherwise synthetic or anonymised data is used."
      },
      {
        "question": "What remains after the course?",
        "answer": "Reusable materials, examples, checklists and a clear set of next steps."
      },
      {
        "question": "Is it theoretical?",
        "answer": "No. The course is built around practical exercises and decisions close to real work."
      }
    ],
    "output": "Operating canvas for secure AI software lifecycle.",
    "searchIntents": [
      "corporate AI course on secure AI software lifecycle",
      "practical training for Secure AI SDLC",
      "AI training for technical teams",
      "Artik Lab path for Operating canvas for secure AI software lifecycle",
      "how to introduce secure AI software lifecycle into company workflows"
    ],
    "needSignals": [
      "secure AI software lifecycle is already discussed internally, but there is no shared method for turning it into practice.",
      "People experiment with AI tools on their own and the company does not yet see comparable criteria, controls and outcomes.",
      "The process connected to secure AI software lifecycle absorbs time, creates manual handoffs or produces outputs that are hard to verify.",
      "Leadership needs to decide whether to invest, train or stop before introducing fragile automation.",
      "The company needs a concrete training outcome: Operating canvas for secure AI software lifecycle."
    ],
    "extraExamples": [
      {
        "title": "From generic training to the real process",
        "description": "A company asks for training on secure AI software lifecycle, but the real issue emerges during mapping: repeated tasks, informal checks and distributed responsibilities. The path uses examples close to daily work and turns training into an initial operating model, not a theory session."
      },
      {
        "title": "From individual experimentation to governed practice",
        "description": "Some people have already found shortcuts with AI while others are blocked. The course creates a shared base: what can be done, what must be reviewed, which data should not be exposed and when escalation is needed. The result is Operating canvas for secure AI software lifecycle."
      },
      {
        "title": "From enthusiasm to decision",
        "description": "Management needs to understand whether secure AI software lifecycle deserves budget and continuity. The lab separates immediate benefits, operational risks and data dependencies. The company leaves with criteria for the next step instead of more isolated demos."
      }
    ],
    "selectionCriteria": [
      "Choose this course if the main need concerns secure AI software lifecycle, not a generic overview of AI.",
      "Prefer it when there is a process, document, workflow or responsibility to work on during training.",
      "Postpone it if there is no internal sponsor yet or if the issue is only buying a software licence.",
      "Pair it with AI Workflow Redesign Lab when the company first needs to understand which processes deserve priority."
    ],
    "limits": [
      "It does not promise full automation or replacement of human responsibility.",
      "It does not require confidential data to be uploaded into unapproved environments.",
      "It is not legal, tax, HR or specialist technical advice when those responsibilities remain with competent functions.",
      "It produces skills, criteria and reusable materials; continued adoption requires sponsorship, governance and internal practice."
    ],
    "relatedCourseIds": [
      "workflow-redesign",
      "rag-engineering",
      "ai-output-quality"
    ],
    "urls": {
      "html": "https://ar-tik.com/en/courses/secure-ai-sdlc.html",
      "markdown": "https://ar-tik.com/en/courses/secure-ai-sdlc.md",
      "dossier": "https://ar-tik.com/en/courses/secure-ai-sdlc-dossier.md",
      "json": "https://ar-tik.com/en/courses/secure-ai-sdlc.json",
      "catalog": "https://ar-tik.com/en/courses/",
      "catalogMarkdown": "https://ar-tik.com/en/courses/index.md"
    }
  }
}