Garkuwar Xygeni

AppSec ɗinku ya tsaya a wurin ajiyar kaya. EDR ɗinku bai fahimci fakitin ba.

Dogara mai cutarwa tana gudanar da rubutun shigarwa da zarar mai haɓaka ya shigar, tun kafin kowa ya san cewa yana da cutarwa. Na'urorin na ...

Wakili mai sauƙi ɗaya · Tashoshin aiki, sabar da masu gudu na CI · Ana gudanar da manufofin a tsakiya

api-security-main

Dakatar da Shi Kafin Ya Fara Aiki. Duk Inda Masu Haɓaka Kake Aiki.

Hana dogaro da rubuce-rubuce masu cutarwa daga ci gaba da gudana ta hanyar kare ƙarshen masu haɓakawa inda hare-hare suka fara.

Toshe shi kafin ya aiwatar

Shield yana katse shigarwar fakitin a ainihin lokaci kuma yana duba su akan bayanan sirri na malware na Xygeni. Ana toshe fakitin mugunta a lokacin shigarwa, ba a yi masa alama a cikin rahoto washegari da safe ba. Haka kuma ya shafi hanyar sadarwa: ana yanke haɗin zuwa kayayyakin more rayuwa da aka sani da mugunta kafin komai ya bar na'urar.

Manufofi ɗaya, kowace wurin aiki

Bayyana ƙa'idodi sau ɗaya kuma Shield yana amfani da su akan kowace na'ura a cikin ƙungiyar ku: mafi ƙarancin shekarun fakitin, ba da izini da ƙin jerin abubuwa, rajistar da aka amince da ita, da wuraren da zirga-zirgar ababen hawa ke zuwa.

Ku riƙe shi daga inda ya fara

Idan wani abu mai mahimmanci ya sauka a ƙarshen hanya, Shield zai iya yanke haɗin hanyar sadarwar wannan injin, ta atomatik ko kuma bisa buƙata, don haka lamarin ya tsaya a kwamfutar tafi-da-gidanka ɗaya maimakon yaɗuwa ta cikin ƙungiyar.

Xygeni Shield capabilities

Wurin Wutar Lantarki na Runtime don Ƙarshen Masu Haɓakawa.

Tashar wuta ta dogara, kafin a sami sa hannu.

Ana katse kowace shigarwar fakiti kuma ana tabbatar da ita a ainihin lokacin. Gargaɗin farko na malware na Xygeni yana kama fakitin mugunta waɗanda kayan aikin da aka dogara da suna har yanzu suna amincewa da su, ba tare da jiran CVE, shawara, ko sa hannu da aka buga ba. Toshewa yana faruwa kafin a fara aiwatar da rubutun shigarwa.

Tsarin shekaru mafi ƙaranci

Hare-haren sarkar samar da kayayyaki mafi sauri suna zuwa da sabbin nau'ikan fakiti. Shield yana ba ku damar toshe fakitin da aka buga kwanan nan fiye da iyakar ku, saita ƙa'ida ta duniya da kuma maye gurbin ta bisa ga yanayin muhalli, da kuma yanke shawara kan abin da zai faru idan ba za a iya tantance ranar bugawa ba: yi gargaɗi da kuma ba da izini, ko toshewa.

Tsaron API - OWASP
Amfani da DevAI tare da ikon sarrafa mai haɓakawa

Ba da izinin jerin abubuwa, ƙin yarda da jerin abubuwa da kuma rajistar da aka amince da ita.

Ka yanke shawara kan abin da masu haɓaka shafinka za su iya ɗauka da kuma daga ina. Ka kiyaye jerin abubuwan da aka ba da izini da kuma waɗanda aka hana, kuma ka iyakance shigarwar zuwa ga rajistar da ƙungiyarka ta amince da ita.

Tacewar Wutar Lantarki ta hanyar sadarwa: wurare masu cutarwa da manufofin ƙasa.

Wannan tsari ya shafi hanyoyin haɗi. Garkuwa tana duba zirga-zirgar da ke fitowa daga ƙarshen hanyar sadarwa da sabbin bayanan sirri na hanyar sadarwa kuma tana yanke haɗi zuwa IPs da yankuna da aka sani da aka zana daga alamun barazana, don haka dashen da ya shiga na'ura ba zai iya isa ga kayayyakin more rayuwa da aka gina don kira ba. Bugu da ƙari, za ku iya iyakance zirga-zirgar zuwa wurare masu haɗari ta hanyar yanayin ƙasa. Kowace hanyar sadarwa da aka toshe ana yin rikodin ta da inda ta yi ƙoƙarin isa.

Tsaron API - OWASP
Amfani da DevAI tare da ikon sarrafa mai haɓakawa

Keɓewa daga ƙarshe, da hannu ko ta atomatik.

Ka ware wata na'ura da aka samu matsala sannan ka rage duk wani zirga-zirgar da ke fita sai dai hanyar wakilin, don haka za ka ci gaba da sarrafa ƙarshen yayin da kake riƙe shi. Kunna yanayin tsoro kuma za a nemi keɓewa ta atomatik da zarar an sami sanarwa mai mahimmanci a kan kowane ƙarshen.

Kayayyakin da aka adana a wurare masu kariya.

Duba kowace tashar aiki, uwar garken da mai gudu ta CI da ke gudanar da wakilin garkuwa, tare da tsarin aikinsa, sigar wakili, matsayinsa na yanzu, lokacin da aka fara gani da ƙarshe, da wurin lasisinsa. Tace ta sunan mai masauki, nau'in ƙarshen ko matsayi.

Tushen mai sarrafa APISEC
Amfani da DevAI tare da ikon sarrafa mai haɓakawa

Sanarwa ta ainihin lokaci tare da shaidar da aka haɗa

Kowace toshewa tana zama abin da ya faru a dandamali, tare da tsananin, tambarin lokaci, ƙarshen abin da ya faru a kai, tsawon lokacin da fallasar ta ɗauki, da kuma ainihin abin da aka toshe: fakitin da sigar, ko wurin da za a kai. Tace ta hanyar tsanani, rukuni, nau'i, kewayon mai amfani ko kwanan wata, da kuma fitarwa.

Hanyar binciken kuɗi a kowane ƙarshen

Kowace ƙarshen da aka kare tana ɗauke da nata hanyar binciken da jerin abubuwan da aka haɗa, don haka zaku iya sake gina abin da ya faru akan takamaiman na'ura lokacin da wani ya tambaya.

Tushen mai sarrafa APISEC
Amfani da DevAI tare da ikon sarrafa mai haɓakawa

Yana aiki inda masu haɓakawa ke aiki a zahiri

Wakili mai sauƙi ɗaya wanda ke rufe wuraren aiki, sabar da masu gudu na CI, tare da kujeru masu iyo don haka ɗaukar hoto yana bin mutanenka maimakon kayan aikinka.

Me ya sa Xygeni

Nemo kuma gyara haɗarin API a cikin lambar kafin su kai ga samarwa.

The gap between your AppSec and your endpoint tooling

Code and dependency scanning analyses the repository. Endpoint tooling watches processes and connections but has no application-security context to interpret a package or a registry. Between those two sits the moment a malicious dependency actually executes, on a developer’s machine. That is where Shield operates.

Prevention, not post-mortem.

Reputation and signature-based approaches tell you about a malicious package once somebody else has already been hit by it. Shield blocks on behaviour and risk analysis, which is what makes it useful on the day an attack is new, and backs it with current network intelligence so anything that does land cannot phone home.

Endpoint enforcement in the same platform as everything else

 Blocks, isolations and geo events land in the same console as your code, dependency, pipeline and secret findings, with one audit trail. Not another agent with another dashboard da kuma wani login.

FAQs

How is Shield different from the EDR we already run?

Endpoint detection watches processes, files and connections at the operating system level. It does not know what a package registry is, whether a dependency is malicious, or whether a version was published yesterday. Shield brings application-security context to the developer endpoint and enforces policy on the things AppSec cares about.

Shield is a lightweight agent that checks installs as they happen. Developers only notice it when something is blocked, and the block comes with the reason.

Malicious and unauthorized package installs, packages that are newer than your minimum-age threshold, installs from registries you have not approved, packages on your deny list, outbound connections to known-malicious IPs and domains, and traffic to geographies you have restricted.

You decide. The minimum-age policy lets you either warn and allow, or block, when the publication date is unknown.

Yes. The global minimum-age threshold can be overridden per ecosystem, and disabled for a specific ecosystem if you need to.

It blocks all outbound traffic from that machine except the Shield agent’s own channel, so the endpoint is contained but still manageable. You can trigger it on demand, or enable paranoid mode so isolation is requested automatically when a critical alert lands.

On developer workstations, on servers, and on CI runners. Licensing uses floating seats.

Yes. Every block is an event with full detail, and each endpoint keeps its own audit trail. Events can be filtered and exported.

Block the Attack on the Machine Where It Lands

tare da Xygeni All-In-One AppSec Platform