3853 - Combining Noname Security with API Connect to solidify DevSecOps and API Governance.pdf

1、October 21-24,2024Mandalay Bay Convention CenterLas Vegas,NevadaSession Code 3853Bryon KiSOA Group,CTOCheryl BiSOA Group,COOCombining Noname securitywith API Connect to solidify DevSecOps and API GovernanceYouve been breached!#IBMTechXchangeMethods we use to prevent an API breachNoname identificatio

2、nAPI DiscoveryFindings/AttacksUpgrade SDLC lifecycleAPI InventoryAPI GovernanceAPI AssistantActive TestingShift LeftDevSecOpsUse WatsonXAssist developerGuidanceCode SamplesCreate API Governance3IBM TechXchange|2024 IBM CorporationA series of steps that divide the software development process into ta

3、sks you can assign,complete,and measure.oCost-effective and Time-efficient processoDesign and build high-quality software.oMinimize project risksoMeets customer expectationsIBM TechXchange|2024 IBM CorporationAPI-Led Lifecycle#IBMTechXchangeHow GenAIAccelerates Issue resolutions5Watsonx.aiWatsonxAss

4、istantWatsonxActionsWatsonxOrchestration-Developer tells Noname working on it-Develop SkillsLLM-Granite-RAG/Fine Tuning-Agents-API Connect Knowledge CenterIBM TechXchange|2024 IBM Corporation#IBMTechXchangeLearning MoreNoname DemoUnderstand how Noname provide API Discovery,validates your Posture Man

5、agement and identifies and remediates attacksNoname Active Testing WorkshopLearn how Active Testing shift left testing can help secure you APIs within a CI/CD pipelineNoname AssessmentLearn,document and prepare to include Noname API Security to your organization6IBM TechXchange|2024 IBM CorporationC

6、ontact iSOA Group to schedule#IBMTechXchange7Thank YouBryon KataokaiSOA Group,CTOIBM TechXchange|2024 IBM Corporation#IBMTechXchangeNotices and disclaimersCertain comments made in this presentation may be characterized as forward looking under the Private Securities Litigation Reform Act of 1995.For