home.social

#secureai โ€” Public Fediverse posts

Live and recent posts from across the Fediverse tagged #secureai, aggregated by home.social.

  1. ๐Ÿš€ Connect4Cyber 2026 โ€“ Info & Brokerage Day

    โ€ข aktuelle #EU-Fรถrdermรถglichkeiten kennenzulernen.
    โ€ข lรคnderรผbergreifende Konsortien aufzubauen.
    โ€ข sich zu Themen wie #SecureAI, #Kryptographie und Software-/Hardware-Security auszutauschen.

    Datum: 23. April 2026
    Ort: World Trade Center, Stockholm

    Die Teilnahme ist kostenlos โ€“ die Plรคtze sind begrenzt. Jetzt registrieren bis zum 13. April!
    ๐Ÿ‘‰ ncc-se.msb.se/en/events/connec

  2. Building a sovereign-ready AI stack that uses public APIs wisely while maintaining a private, compliant intelligence engine. Strategy over subscription. #SecureAI #IntelligentSystems ironwoodlogic.com/articles/bey

  3. High-growth doesn't have to mean high-touch. Learn how a professional services firm reduced founder involvement by 65% while scaling operations. #SecureAI #CloudArchitecture ironwoodlogic.com/case-studies

  4. Check out ห—หห‹ โญ’ lnkd.in/gE2wUqgc โญ’ หŽหŠห— to see my intro whilst you listen.

    I'm thus re-naming this work as "CVE Keeper - Security at x+1; rethinking vulnerability management beyond CVSS & scanners". I must also thank @andrewpollock for reviewing several of my verbose drafts. ๐Ÿซก

    So, Security at x+1; rethinking vulnerability management beyond CVSS & scanners -

    Most vulnerability tooling today is optimized for disclosure and alert volume, not for making correct decisions on real systems. CVEs arrive faster than teams can evaluate them, scores are generic, context arrives late, and we still struggle to answer the only question that matters: does this actually put my system at risk right now?

    Over the last few years working close to CVE lifecycle automation, Iโ€™ve been designing an open architecture that treats vulnerability management as a continuous, system-specific reasoning problem rather than a static scoring task. The goal is to assess impact on the same day for 0-days using minimal upstream data, refine accuracy over time as context improves, reason across dependencies and compound vulnerabilities, and couple automation with explicit human verification instead of replacing it.

    This work explores:

    โค‡ 1โ€ข Same-day triage of newly disclosed and 0-day vulnerabilities
    โค‡ 2โ€ข Dependency-aware and compound vulnerability impact assessment
    โค‡ 3โ€ข Correlating classical CVSS with AI-specific threat vectors
    โค‡ 4โ€ข Reducing operational noise, unnecessary reboots, and security burnout
    โค‡ 5โ€ข Making high-quality vulnerability intelligence accessible beyond enterprise teams

    The core belief is simple: most security failures come from misjudged impact, not missed vulnerabilities. Accuracy, context, and accountability matter more than volume.

    Iโ€™m sharing this to invite feedback from folks working in CVE, OSV, vulnerability disclosure, AI security, infra, and systems research. Disagreement and critique are welcome. This problem affects everyone, and I donโ€™t think incremental tooling alone will solve it.

    P.S.

    • Super appreciate everyone that's spent time reviewing my drafts and reading all my essays lol. I owe you ๐Ÿซถ๐Ÿป
    • ... and GoogleLM. These slides would have taken me forever to make otherwise.

    Take my CVE-data User Survey to allow me to tailor your needs into my design - lnkd.in/gcyvnZeE
    See more at - lnkd.in/gGWQfBW5
    lnkd.in/gE2wUqgc

    #VulnerabilityManagement #Risk #ThreatModeling #CVE #CyberSecurity #Infosec #VulnerabilityManagement #ThreatIntelligence #ApplicationSecurity #SecurityOperations #ZeroDay #RiskManagement #DevSecOps #CVE #CVEAnalysis #VulnerabilityDisclosure #SecurityData #CVSS #VulnerabilityAssessment #PatchManagement #AI #AIML #AISecurity #MachineLearning #AIThreats #AIinSecurity #SecureAI #OSS #Rust #ZeroTrust #Security

    linkedin.com/feed/update/urn:l

  5. Check out ห—หห‹ โญ’ lnkd.in/gE2wUqgc โญ’ หŽหŠห— to see my intro whilst you listen.

    I'm thus re-naming this work as "CVE Keeper - Security at x+1; rethinking vulnerability management beyond CVSS & scanners". I must also thank @andrewpollock for reviewing several of my verbose drafts. ๐Ÿซก

    So, Security at x+1; rethinking vulnerability management beyond CVSS & scanners -

    Most vulnerability tooling today is optimized for disclosure and alert volume, not for making correct decisions on real systems. CVEs arrive faster than teams can evaluate them, scores are generic, context arrives late, and we still struggle to answer the only question that matters: does this actually put my system at risk right now?

    Over the last few years working close to CVE lifecycle automation, Iโ€™ve been designing an open architecture that treats vulnerability management as a continuous, system-specific reasoning problem rather than a static scoring task. The goal is to assess impact on the same day for 0-days using minimal upstream data, refine accuracy over time as context improves, reason across dependencies and compound vulnerabilities, and couple automation with explicit human verification instead of replacing it.

    This work explores:

    โค‡ 1โ€ข Same-day triage of newly disclosed and 0-day vulnerabilities
    โค‡ 2โ€ข Dependency-aware and compound vulnerability impact assessment
    โค‡ 3โ€ข Correlating classical CVSS with AI-specific threat vectors
    โค‡ 4โ€ข Reducing operational noise, unnecessary reboots, and security burnout
    โค‡ 5โ€ข Making high-quality vulnerability intelligence accessible beyond enterprise teams

    The core belief is simple: most security failures come from misjudged impact, not missed vulnerabilities. Accuracy, context, and accountability matter more than volume.

    Iโ€™m sharing this to invite feedback from folks working in CVE, OSV, vulnerability disclosure, AI security, infra, and systems research. Disagreement and critique are welcome. This problem affects everyone, and I donโ€™t think incremental tooling alone will solve it.

    P.S.

    • Super appreciate everyone that's spent time reviewing my drafts and reading all my essays lol. I owe you ๐Ÿซถ๐Ÿป
    • ... and GoogleLM. These slides would have taken me forever to make otherwise.

    Take my CVE-data User Survey to allow me to tailor your needs into my design - lnkd.in/gcyvnZeE
    See more at - lnkd.in/gGWQfBW5
    lnkd.in/gE2wUqgc

    #VulnerabilityManagement #Risk #ThreatModeling #CVE #CyberSecurity #Infosec #VulnerabilityManagement #ThreatIntelligence #ApplicationSecurity #SecurityOperations #ZeroDay #RiskManagement #DevSecOps #CVE #CVEAnalysis #VulnerabilityDisclosure #SecurityData #CVSS #VulnerabilityAssessment #PatchManagement #AI #AIML #AISecurity #MachineLearning #AIThreats #AIinSecurity #SecureAI #OSS #Rust #ZeroTrust #Security

    linkedin.com/feed/update/urn:l

  6. Check out ห—หห‹ โญ’ lnkd.in/gE2wUqgc โญ’ หŽหŠห— to see my intro whilst you listen.

    I'm thus re-naming this work as "CVE Keeper - Security at x+1; rethinking vulnerability management beyond CVSS & scanners". I must also thank @andrewpollock for reviewing several of my verbose drafts. ๐Ÿซก

    So, Security at x+1; rethinking vulnerability management beyond CVSS & scanners -

    Most vulnerability tooling today is optimized for disclosure and alert volume, not for making correct decisions on real systems. CVEs arrive faster than teams can evaluate them, scores are generic, context arrives late, and we still struggle to answer the only question that matters: does this actually put my system at risk right now?

    Over the last few years working close to CVE lifecycle automation, Iโ€™ve been designing an open architecture that treats vulnerability management as a continuous, system-specific reasoning problem rather than a static scoring task. The goal is to assess impact on the same day for 0-days using minimal upstream data, refine accuracy over time as context improves, reason across dependencies and compound vulnerabilities, and couple automation with explicit human verification instead of replacing it.

    This work explores:

    โค‡ 1โ€ข Same-day triage of newly disclosed and 0-day vulnerabilities
    โค‡ 2โ€ข Dependency-aware and compound vulnerability impact assessment
    โค‡ 3โ€ข Correlating classical CVSS with AI-specific threat vectors
    โค‡ 4โ€ข Reducing operational noise, unnecessary reboots, and security burnout
    โค‡ 5โ€ข Making high-quality vulnerability intelligence accessible beyond enterprise teams

    The core belief is simple: most security failures come from misjudged impact, not missed vulnerabilities. Accuracy, context, and accountability matter more than volume.

    Iโ€™m sharing this to invite feedback from folks working in CVE, OSV, vulnerability disclosure, AI security, infra, and systems research. Disagreement and critique are welcome. This problem affects everyone, and I donโ€™t think incremental tooling alone will solve it.

    P.S.

    • Super appreciate everyone that's spent time reviewing my drafts and reading all my essays lol. I owe you ๐Ÿซถ๐Ÿป
    • ... and GoogleLM. These slides would have taken me forever to make otherwise.

    Take my CVE-data User Survey to allow me to tailor your needs into my design - lnkd.in/gcyvnZeE
    See more at - lnkd.in/gGWQfBW5
    lnkd.in/gE2wUqgc

    #VulnerabilityManagement #Risk #ThreatModeling #CVE #CyberSecurity #Infosec #VulnerabilityManagement #ThreatIntelligence #ApplicationSecurity #SecurityOperations #ZeroDay #RiskManagement #DevSecOps #CVE #CVEAnalysis #VulnerabilityDisclosure #SecurityData #CVSS #VulnerabilityAssessment #PatchManagement #AI #AIML #AISecurity #MachineLearning #AIThreats #AIinSecurity #SecureAI #OSS #Rust #ZeroTrust #Security

    linkedin.com/feed/update/urn:l

  7. Check out ห—หห‹ โญ’ lnkd.in/gE2wUqgc โญ’ หŽหŠห— to see my intro whilst you listen.

    I'm thus re-naming this work as "CVE Keeper - Security at x+1; rethinking vulnerability management beyond CVSS & scanners". I must also thank @andrewpollock for reviewing several of my verbose drafts. ๐Ÿซก

    So, Security at x+1; rethinking vulnerability management beyond CVSS & scanners -

    Most vulnerability tooling today is optimized for disclosure and alert volume, not for making correct decisions on real systems. CVEs arrive faster than teams can evaluate them, scores are generic, context arrives late, and we still struggle to answer the only question that matters: does this actually put my system at risk right now?

    Over the last few years working close to CVE lifecycle automation, Iโ€™ve been designing an open architecture that treats vulnerability management as a continuous, system-specific reasoning problem rather than a static scoring task. The goal is to assess impact on the same day for 0-days using minimal upstream data, refine accuracy over time as context improves, reason across dependencies and compound vulnerabilities, and couple automation with explicit human verification instead of replacing it.

    This work explores:

    โค‡ 1โ€ข Same-day triage of newly disclosed and 0-day vulnerabilities
    โค‡ 2โ€ข Dependency-aware and compound vulnerability impact assessment
    โค‡ 3โ€ข Correlating classical CVSS with AI-specific threat vectors
    โค‡ 4โ€ข Reducing operational noise, unnecessary reboots, and security burnout
    โค‡ 5โ€ข Making high-quality vulnerability intelligence accessible beyond enterprise teams

    The core belief is simple: most security failures come from misjudged impact, not missed vulnerabilities. Accuracy, context, and accountability matter more than volume.

    Iโ€™m sharing this to invite feedback from folks working in CVE, OSV, vulnerability disclosure, AI security, infra, and systems research. Disagreement and critique are welcome. This problem affects everyone, and I donโ€™t think incremental tooling alone will solve it.

    P.S.

    • Super appreciate everyone that's spent time reviewing my drafts and reading all my essays lol. I owe you ๐Ÿซถ๐Ÿป
    • ... and GoogleLM. These slides would have taken me forever to make otherwise.

    Take my CVE-data User Survey to allow me to tailor your needs into my design - lnkd.in/gcyvnZeE
    See more at - lnkd.in/gGWQfBW5
    lnkd.in/gE2wUqgc

    #VulnerabilityManagement #Risk #ThreatModeling #CVE #CyberSecurity #Infosec #VulnerabilityManagement #ThreatIntelligence #ApplicationSecurity #SecurityOperations #ZeroDay #RiskManagement #DevSecOps #CVE #CVEAnalysis #VulnerabilityDisclosure #SecurityData #CVSS #VulnerabilityAssessment #PatchManagement #AI #AIML #AISecurity #MachineLearning #AIThreats #AIinSecurity #SecureAI #OSS #Rust #ZeroTrust #Security

    linkedin.com/feed/update/urn:l

  8. ๐ŸŽ™๏ธ When AI writes code, builds models, and simulates threatsโ€ฆ who checks the checker?

    In this last On Location Conversation from #RSAC2025, Alex Kreilein and John Sapp Jr. join Sean Martin, CISSP to explore what trust actually means in the age of AI-generated security tooling โ€” and how modern #AppSec teams must rethink validation, #resiliency, and #risk.

    This episode cuts deep into:

    Why โ€œtrust the outputโ€ is not enough in AI-driven workflows
    How #AI security debt is becoming the new tech debt
    Why we need #zerotrust thinking applied to models and agents
    The real shift: from patching CVEs to building resilient architecture
    The role of traceability, governance, and context-driven decision-making

    If youโ€™re serious about secure AI, application security, and shifting AppSec left (the right way), this conversation will challenge what you think you know โ€” and help reframe what secure development actually looks like.

    ๐ŸŽฅ Watch the full video:
    ๐Ÿ‘‰ youtu.be/kJdQz9LmT6s

    ๐ŸŽง Listen to the audio podcast:
    ๐Ÿ‘‰ eventcoveragepodcast.com/episo

    โœจ Thank you to our Full Coverage Sponsors:
    ThreatLocker ๐Ÿ‘‰ itspm.ag/threatlocker-r974
    Akamai Technologies ๐Ÿ‘‰ itspm.ag/akamailbwc
    BLACKCLOAK ๐Ÿ‘‰ itspm.ag/itspbcweb
    SandboxAQ ๐Ÿ‘‰ itspm.ag/sandboxaq-j2en
    Archer Integrated Risk Management ๐Ÿ‘‰ itspm.ag/rsaarchweb
    ISACA ๐Ÿ‘‰ itspm.ag/isaca-96808
    Object First ๐Ÿ‘‰ itspm.ag/object-first-2gjl
    Edera ๐Ÿ‘‰ itspm.ag/edera-434868

    ๐ŸŽ™๏ธ Explore more RSAC 2025 coverage:
    ๐Ÿ‘‰ itspmagazine.com/rsa-conferenc

    ๐ŸŽง Catch all of our event conversations:
    ๐Ÿ‘‰ itspmagazine.com/technology-an

    ๐ŸŽค Want to tell your Brand Story Briefing as part of our coverage?
    ๐Ÿ‘‰ itspm.ag/evtcovbrf

    ๐Ÿ“† Want Sean Martin, CISSP and Marco Ciappelli to cover your event or moderate your panel?
    ๐Ÿ‘‰ itspmagazine.com/contact-us

    #RSAC2025 #cybersecurity #AppSec #AIsecurity #zerotrust #infosec #securityleadership #riskmanagement #technology #eventcoverage #secureAI #shiftleft #CISO

  9. Join Javan Rasokat and Rico Komenda at OWASP Global AppSec EU 2025 in Barcelona for a powerful joint session on AI security!

    ๐Ÿ› ๏ธBuilders and Breakers: A Collaborative Look at Securing LLM-Integrated Apps
    ๐Ÿ“… Thursday, May 29, 2025
    โฐ 2:15 PM โ€“ 3:00 PM CEST

    ๐Ÿ”— Register: owasp.glueup.com/event/123983/

    #OWASP #AppSecEU2025 #AIsecurity #LLMSecurity #Cybersecurity #RedTeam #BlueTeam #SecureAI #Barcelona

  10. Join Javan Rasokat and Rico Komenda at OWASP Global AppSec EU 2025 in Barcelona for a powerful joint session on AI security!

    ๐Ÿ› ๏ธBuilders and Breakers: A Collaborative Look at Securing LLM-Integrated Apps
    ๐Ÿ“… Thursday, May 29, 2025
    โฐ 2:15 PM โ€“ 3:00 PM CEST

    ๐Ÿ”— Register: owasp.glueup.com/event/123983/

    #OWASP #AppSecEU2025 #AIsecurity #LLMSecurity #Cybersecurity #RedTeam #BlueTeam #SecureAI #Barcelona

  11. Join Javan Rasokat and Rico Komenda at OWASP Global AppSec EU 2025 in Barcelona for a powerful joint session on AI security!

    ๐Ÿ› ๏ธBuilders and Breakers: A Collaborative Look at Securing LLM-Integrated Apps
    ๐Ÿ“… Thursday, May 29, 2025
    โฐ 2:15 PM โ€“ 3:00 PM CEST

    ๐Ÿ”— Register: owasp.glueup.com/event/123983/

    #OWASP #AppSecEU2025 #AIsecurity #LLMSecurity #Cybersecurity #RedTeam #BlueTeam #SecureAI #Barcelona

  12. Join Javan Rasokat and Rico Komenda at OWASP Global AppSec EU 2025 in Barcelona for a powerful joint session on AI security!

    ๐Ÿ› ๏ธBuilders and Breakers: A Collaborative Look at Securing LLM-Integrated Apps
    ๐Ÿ“… Thursday, May 29, 2025
    โฐ 2:15 PM โ€“ 3:00 PM CEST

    ๐Ÿ”— Register: owasp.glueup.com/event/123983/

    #OWASP #AppSecEU2025 #AIsecurity #LLMSecurity #Cybersecurity #RedTeam #BlueTeam #SecureAI #Barcelona

  13. Join Javan Rasokat and Rico Komenda at OWASP Global AppSec EU 2025 in Barcelona for a powerful joint session on AI security!

    ๐Ÿ› ๏ธBuilders and Breakers: A Collaborative Look at Securing LLM-Integrated Apps
    ๐Ÿ“… Thursday, May 29, 2025
    โฐ 2:15 PM โ€“ 3:00 PM CEST

    ๐Ÿ”— Register: owasp.glueup.com/event/123983/

    #OWASP #AppSecEU2025 #AIsecurity #LLMSecurity #Cybersecurity #RedTeam #BlueTeam #SecureAI #Barcelona

  14. ๐Ÿค– AI is revolutionising everything it seems - but are you ready for the risks it brings? ๐Ÿค–

    Iโ€™ve been working with AI tools like Copilot and ChatGPT, as well as building an innovative risk management platform which boasts a responsible and proportionate use of AI to enhance human endeavour, rather than seeking to mimic or replace it.

    AI is transforming how we work, but it also exposes us to new risks. In my latest article, I outline the YDC approach to managing AI cybersecurity risks - from validation processes to risk assessments, and share my thoughts on how we can strike the balance between leveraging AI's potential and safeguarding our systems.

    Interested? Check it out here - paulreynolds.uk/cybersecurity-

    YDC keep pushing the boundaries of innovation, embracing AI, while keeping security on point.

    #Cybersecurity #AI #ArtificialIntelligence #AICybersecurityRisks #DataProtection #Innovation #TechLeadership #RiskManagement
    #FutureOfWork #DigitalSecurity #SecureAI

  15. Coalition for Secure AI (CoSAI): An open ecosystem uniting AI and security experts from leading organizations. CoSAI fosters collaboration on AI security research, shares best practices, and develops open-source solutions for secure AI deployment.

    #AI #Cybersecurity #AIResearch #SecureAI #TechCollaboration #OpenSource #CoSAI #DigitalSecurity

    coalitionforsecureai.org/

  16. โ“ Did you know that with open-access LLMs, entities in sectors like health ๐Ÿฅ and banking ๐Ÿฆ can use AI securely without risking data privacy? Participants are learning how to leverage models like Falcon and Mistral 7B locally for safe applications! #SecureAI

  17. ๐€๐ง๐ง๐จ๐ฎ๐ง๐œ๐ข๐ง๐  ๐Œ๐ข๐œ๐ซ๐จ๐ฌ๐จ๐Ÿ๐ญโ€™๐ฌ ๐จ๐ฉ๐ž๐ง ๐š๐ฎ๐ญ๐จ๐ฆ๐š๐ญ๐ข๐จ๐ง ๐Ÿ๐ซ๐š๐ฆ๐ž๐ฐ๐จ๐ซ๐ค ๐ญ๐จ ๐ซ๐ž๐ ๐ญ๐ž๐š๐ฆ ๐ ๐ž๐ง๐ž๐ซ๐š๐ญ๐ข๐ฏ๐ž ๐€๐ˆ ๐’๐ฒ๐ฌ๐ญ๐ž๐ฆ๐ฌ

    ๐๐ฒ๐‘๐ˆ๐“ automates AI Red Teaming tasks to allow operators to focus on more complicated and time-consuming tasks and can also identify security harms such as misuse (e.g., malware generation, jailbreaking), and privacy harms (e.g., identity theft).โ€‹

    Find out more:

    microsoft.com/en-us/security/b

    GitHub repo: github.com/Azure/PyRIT

    How to Guide: github.com/Azure/PyRIT/blob/ma

    #redteam #airedteam #redteaming #PyRIT #ml #ai #framewrok #python #cyber #llm #ai #aisecurity #microsoft #microsoftsecurity #opensource #MicrosoftAIRedTeam #GenAI #jailbreaking #promtp #promptinjection #malware #privacy #responsibleai #cybersecurity #aisecurity #secureai #machinelearning #generativeai

  18. ๐€๐ง๐ง๐จ๐ฎ๐ง๐œ๐ข๐ง๐  ๐Œ๐ข๐œ๐ซ๐จ๐ฌ๐จ๐Ÿ๐ญโ€™๐ฌ ๐จ๐ฉ๐ž๐ง ๐š๐ฎ๐ญ๐จ๐ฆ๐š๐ญ๐ข๐จ๐ง ๐Ÿ๐ซ๐š๐ฆ๐ž๐ฐ๐จ๐ซ๐ค ๐ญ๐จ ๐ซ๐ž๐ ๐ญ๐ž๐š๐ฆ ๐ ๐ž๐ง๐ž๐ซ๐š๐ญ๐ข๐ฏ๐ž ๐€๐ˆ ๐’๐ฒ๐ฌ๐ญ๐ž๐ฆ๐ฌ

    ๐๐ฒ๐‘๐ˆ๐“ automates AI Red Teaming tasks to allow operators to focus on more complicated and time-consuming tasks and can also identify security harms such as misuse (e.g., malware generation, jailbreaking), and privacy harms (e.g., identity theft).โ€‹

    Find out more:

    microsoft.com/en-us/security/b

    GitHub repo: github.com/Azure/PyRIT

    How to Guide: github.com/Azure/PyRIT/blob/ma

    #redteam #airedteam #redteaming #PyRIT #ml #ai #framewrok #python #cyber #llm #ai #aisecurity #microsoft #microsoftsecurity #opensource #MicrosoftAIRedTeam #GenAI #jailbreaking #promtp #promptinjection #malware #privacy #responsibleai #cybersecurity #aisecurity #secureai #machinelearning #generativeai

  19. ๐€๐ง๐ง๐จ๐ฎ๐ง๐œ๐ข๐ง๐  ๐Œ๐ข๐œ๐ซ๐จ๐ฌ๐จ๐Ÿ๐ญโ€™๐ฌ ๐จ๐ฉ๐ž๐ง ๐š๐ฎ๐ญ๐จ๐ฆ๐š๐ญ๐ข๐จ๐ง ๐Ÿ๐ซ๐š๐ฆ๐ž๐ฐ๐จ๐ซ๐ค ๐ญ๐จ ๐ซ๐ž๐ ๐ญ๐ž๐š๐ฆ ๐ ๐ž๐ง๐ž๐ซ๐š๐ญ๐ข๐ฏ๐ž ๐€๐ˆ ๐’๐ฒ๐ฌ๐ญ๐ž๐ฆ๐ฌ

    ๐๐ฒ๐‘๐ˆ๐“ automates AI Red Teaming tasks to allow operators to focus on more complicated and time-consuming tasks and can also identify security harms such as misuse (e.g., malware generation, jailbreaking), and privacy harms (e.g., identity theft).โ€‹

    Find out more:

    microsoft.com/en-us/security/b

    GitHub repo: github.com/Azure/PyRIT

    How to Guide: github.com/Azure/PyRIT/blob/ma

    #redteam #airedteam #redteaming #PyRIT #ml #ai #framewrok #python #cyber #llm #ai #aisecurity #microsoft #microsoftsecurity #opensource #MicrosoftAIRedTeam #GenAI #jailbreaking #promtp #promptinjection #malware #privacy #responsibleai #cybersecurity #aisecurity #secureai #machinelearning #generativeai

  20. ๐€๐ง๐ง๐จ๐ฎ๐ง๐œ๐ข๐ง๐  ๐Œ๐ข๐œ๐ซ๐จ๐ฌ๐จ๐Ÿ๐ญโ€™๐ฌ ๐จ๐ฉ๐ž๐ง ๐š๐ฎ๐ญ๐จ๐ฆ๐š๐ญ๐ข๐จ๐ง ๐Ÿ๐ซ๐š๐ฆ๐ž๐ฐ๐จ๐ซ๐ค ๐ญ๐จ ๐ซ๐ž๐ ๐ญ๐ž๐š๐ฆ ๐ ๐ž๐ง๐ž๐ซ๐š๐ญ๐ข๐ฏ๐ž ๐€๐ˆ ๐’๐ฒ๐ฌ๐ญ๐ž๐ฆ๐ฌ

    ๐๐ฒ๐‘๐ˆ๐“ automates AI Red Teaming tasks to allow operators to focus on more complicated and time-consuming tasks and can also identify security harms such as misuse (e.g., malware generation, jailbreaking), and privacy harms (e.g., identity theft).โ€‹

    Find out more:

    microsoft.com/en-us/security/b

    GitHub repo: github.com/Azure/PyRIT

    How to Guide: github.com/Azure/PyRIT/blob/ma

    #redteam #airedteam #redteaming #PyRIT #ml #ai #framewrok #python #cyber #llm #ai #aisecurity #microsoft #microsoftsecurity #opensource #MicrosoftAIRedTeam #GenAI #jailbreaking #promtp #promptinjection #malware #privacy #responsibleai #cybersecurity #aisecurity #secureai #machinelearning #generativeai

  21. ๐€๐ง๐ง๐จ๐ฎ๐ง๐œ๐ข๐ง๐  ๐Œ๐ข๐œ๐ซ๐จ๐ฌ๐จ๐Ÿ๐ญโ€™๐ฌ ๐จ๐ฉ๐ž๐ง ๐š๐ฎ๐ญ๐จ๐ฆ๐š๐ญ๐ข๐จ๐ง ๐Ÿ๐ซ๐š๐ฆ๐ž๐ฐ๐จ๐ซ๐ค ๐ญ๐จ ๐ซ๐ž๐ ๐ญ๐ž๐š๐ฆ ๐ ๐ž๐ง๐ž๐ซ๐š๐ญ๐ข๐ฏ๐ž ๐€๐ˆ ๐’๐ฒ๐ฌ๐ญ๐ž๐ฆ๐ฌ

    ๐๐ฒ๐‘๐ˆ๐“ automates AI Red Teaming tasks to allow operators to focus on more complicated and time-consuming tasks and can also identify security harms such as misuse (e.g., malware generation, jailbreaking), and privacy harms (e.g., identity theft).โ€‹

    Find out more:

    microsoft.com/en-us/security/b

    GitHub repo: github.com/Azure/PyRIT

    How to Guide: github.com/Azure/PyRIT/blob/ma

    #redteam #airedteam #redteaming #PyRIT #ml #ai #framewrok #python #cyber #llm #ai #aisecurity #microsoft #microsoftsecurity #opensource #MicrosoftAIRedTeam #GenAI #jailbreaking #promtp #promptinjection #malware #privacy #responsibleai #cybersecurity #aisecurity #secureai #machinelearning #generativeai