If you are not sure if the website you would like to visit is secure, you can verify it here. Enter the website address of the page and see parts of its content and the thumbnail images on this site. None (if any) dangerous scripts on the referenced page will be executed. Additionally, if the selected site contains subpages, you can verify it (review) in batches containing 5 pages.
favicon.ico: web.archive.org/web/20230202224029/https://github.com/customer-stories/zibasec - ZibaSec · GitHub.

site address: web.archive.org/web/20230202172754/https://github.com/customer-stories/zibasec redirected to: web.archive.org/web/20230202224029/https://github.com/customer-stories/zibasec

site title: ZibaSec · GitHub

Our opinion (on Saturday 26 September 2026 23:21:14 UTC):

GREEN status (no comments) - no comments
After content analysis of this website we propose the following hashtags:



Meta tags:
description=ZibaSec achieves great feats with a small team to protect federal organizations from phishing attacks.;

Headings (most frequently used words):

github, team, from, zibasec, achieves, great, feats, with, small, to, protect, federal, organizations, phishing, attacks, product, platform, support, company, explore, more, what, will, your, story, be, the, readme, project, copilot, actions, free, enterprise,

Text of the page (most frequently used words):
#github (56), the (55), and (41), that (25), for (24), with (22), team (21), zibasec (20), security (14), more (13), your (12), #actions (12), enterprise (11), can (10), about (10), they (10), fedramp (10), any (10), organizations (8), from (8), code (8), was (8), are (8), their (8), through (8), into (8), work (8), all (8), you (7), said (7), open (7), federal (7), when (7), this (6), customer (6), stories (6), want (6), start (6), have (6), source (6), data (6), changes (6), access (6), out (5), time (5), what (5), organization (5), advanced (5), production (5), other (5), than (5), repository (5), because (5), documentation (5), false (5), tools (5), process (5), vulnerability (5), tool (5), jump (5), company (4), community (4), readme (4), project (4), use (4), our (4), per (4), month (4), free (4), just (4), would (4), seven (4), drake (4), there (4), don (4), issues (4), like (4), many (4), issue (4), aws (4), change (4), phishing (4), search (4), api (3), features (3), own (3), individuals (3), create (3), learn (3), workflow (3), copilot (3), trial (3), able (3), possible (3), people (3), but (3), while (3), important (3), haven (3), run (3), positives (3), find (3), going (3), has (3), even (3), serverless (3), them (3), davila (3), detected (3), needs (3), documented (3), shepherd (3), these (3), request (3), using (3), approval (3), once (3), approved (3), allows (3), control (3), could (3), now (3), made (3), small (3), ccb (3), attacks (3), vulnerabilities (3), sign (3), signed (2), another (2), tab (2), window (2), refresh (2), session (2), reload (2), 2022 (2), 2023 (2), blog (2), skills (2), services (2), developer (2), resources (2), pricing (2), product (2), plans (2), collaboration (2), will (2), story (2), automate (2), write (2), explore (2), days (2), huge (2), accomplishment (2), far (2), part (2), success (2), some (2), secure (2), being (2), standard (2), communities (2), trust (2), provide (2), still (2), world (2), hosts (2), repositories (2), well (2), accuracy (2), crucial (2), spend (2), writing (2), help (2), rather (2), saved (2), cloud (2), its (2), physical (2), servers (2), regulations (2), not (2), managing (2), been (2), meet (2), requirements (2), without (2), stated (2), requires (2), addressed (2), positive (2), need (2), static (2), analysis (2), helped (2), had (2), found (2), opened (2), closed (2), tracking (2), particularly (2), agencies (2), uses (2), automation (2), every (2), pull (2), results (2), created (2), off (2), technology (2), including (2), rules (2), everything (2), slow (2), person (2), requested (2), task (2), system (2), broker (2), were (2), founder (2), track (2), much (2), larger (2), creates (2), files (2), then (2), message (2), companies (2), must (2), certification (2), stakeholders (2), operations (2), which (2), service (2), government (2), cyber (2), cybersecurity (2), products (2), scan (2), better (2), manage (2), packages (2), web (2), sep (2), perform, action, git, site, map, updated, privacy, terms, inc, tiktok, twitch, youtube, linkedin, facebook, twitter, shop, social, impact, inclusion, press, careers, contact, status, professional, forum, docs, support, desktop, electron, partners, platform, roadmap, check, compliance, flexible, deployment, continue, basics, collaborating, idea, pair, programmer, helps, faster, voices, curious, increase, user, after, expires, interested, bringing, traditional, flexibility, provided, function, level, mature, achieve, seem, gotten, deserves, credit, think, very, valuable, practice, learning, building, public, refrain, potential, missteps, benefits, outweigh, risks, realize, simultaneously, sourced, facto, environment, high, priority, value, importance, where, transparency, almost, non, existent, feel, transparent, end, users, number, contributes, contributions, doesn, centers, machines, regarding, apply, does, bear, responsibility, scanning, server, size, highly, unlikely, model, entrusting, vendors, hours, dollars, lot, considered, legitimate, finding, turns, consuming, avoid, previously, used, generated, unnecessary, due, resolved, within, certain, timeframe, depending, severity, detailed, mechanism, show, auditors, patched, discarded, comes, surprise, working, ensure, nothing, slips, past, attention, runs, checks, displays, also, piggybacks, dependabot, order, facilitate, reporting, extracts, reports, native, interface, clearly, extract, artifacts, audit, love, limited, choice, says, library, pre, built, makes, easy, integrate, customize, ecosystem, currently, terraform, framework, combined, enable, automatic, deploys, multiple, layers, several, branch, protection, merged, kick, deploy, maintain, thorough, record, having, down, didn, depend, single, wearing, hats, sit, ticket, backlog, half, office, instead, automated, anyone, someone, approvals, grants, temporary, account, accessed, suite, saml, integration, alleviate, concerns, might, young, minimize, amount, place, let, grant, way, controlled, versioned, decided, options, really, bad, dan, cto, needed, version, document, sense, already, things, despite, ways, make, most, speeding, automating, notifications, powered, template, filled, concatenates, raw, different, commits, back, bash, script, markdown, templates, required, format, copied, essentially, modernized, historically, paper, three, ring, binder, victoria, director, engineering, meeting, difficult, large, strict, processes, adhere, example, board, integral, typically, various, such, manager, application, owner, engineers, whoever, requesting, effects, reviewed, before, pushed, moving, involved, remote, build, complex, software, becoming, certified, providers, hold, business, standpoint, opens, door, agency, especially, julie, ceo, hardly, ups, space, exclusively, delivered, volunteer, attack, concept, may, sound, strange, exactly, businesses, utilize, today, increasingly, digital, ever, research, shown, email, enables, simulate, sophisticated, campaigns, against, workforce, human, resulting, defend, actual, 2019, since, industry, alexandria, location, achieves, great, feats, protect, suggested, collections, trending, topics, articles, fund, developers, sponsors, case, studies, devsecops, devops, solution, education, startups, teams, solutions, collaborate, outside, discussions, plan, review, instant, dev, environments, codespaces, fix, host, toggle, navigation, skip, content, wayback, machine, http, archive, org, 20230202224029, https, com, timestamps, capture, fail, 2024, mar, feb, jan, 2020, 2026, 083, captures,


Text of the page (random words):
zibasec github 1 083 captures 16 sep 2020 22 sep 2026 jan feb mar 02 2022 2023 2024 success fail about this capture timestamps the wayback machine http web archive org web 20230202224029 https github com customer stories zibasec skip to content toggle navigation sign up product actions automate any workflow packages host and manage packages security find and fix vulnerabilities codespaces instant dev environments copilot write better code with ai code review manage code changes issues plan and track work discussions collaborate outside of code explore all features documentation github skills blog solutions for enterprise teams startups education by solution ci cd automation devops devsecops case studies customer stories resources open source github sponsors fund open source developers the readme project github community articles repositories topics trending collections pricing search all github jump to no suggested jump to results search all github jump to search all github jump to search all github jump to sign in sign up message customer stories enterprise team all stories start a free trial github enterprise zibasec achieves great feats with a small team to protect federal organizations from phishing attacks location alexandria va industry cybersecurity customer since 2019 products github enterprise github advanced security github actions would you volunteer your company for a cyber attack while that concept may sound strange that is exactly what businesses and government organizations utilize zibasec to do in today s increasingly digital world cybersecurity is much more important now more than ever research has shown that 91 of all cyber attacks start with a phishing email while there are many products and services that scan servers and code for vulnerabilities zibasec enables organizations to simulate sophisticated phishing campaigns against their own workforce to scan for human vulnerabilities the resulting data allows them to better defend their organization from actual phishing attacks with a small remote team of seven zibasec has been able to build its complex software and is in the process of becoming fedramp certified which allows cloud service providers to work with federal agencies and hold federal data from a business standpoint the fedramp certification opens the door for them to work with just about any agency in the federal government that was a huge accomplishment for us especially as a start up said julie davila ceo and co founder there are hardly any start ups in the federal space that are exclusively delivered as a service meeting fedramp regulations is a difficult task even for large companies there are many rules and strict processes companies must adhere to for example the change control board ccb is an integral part of the fedramp certification it is typically made up of various stakeholders such as an operations manager application owner security team engineers and whoever is requesting the change which could be the customer all the requested changes including any possible effects on security or operations must be documented reviewed and approved by the ccb before these changes can be pushed into production this can be a slow moving process particularly for larger organizations with more stakeholders involved despite being a small team zibasec found ways to make the most of their workflow like speeding up their ccb process by automating notifications and approval tracking through a repository powered by github actions this system creates a standard template to be filled out concatenates raw data into different files then commits the files back into the repository when a change needs to be made a bash script creates markdown templates in the required format these can then be copied into a pull request message on github for approval we ve essentially modernized a historically paper and three ring binder process using a github repository said victoria drake director of engineering zibasec decided to use github because the other options were really bad stated dan shepherd cto and co founder of zibasec they needed a tool that had version control to track and document every change it just made sense said shepherd we were already using github for other things we now use github actions to work like a much larger team the zibasec team didn t want to depend on any single person to control access to production with a team of seven wearing many hats a requested task could sit in a ticket backlog or half the team could be out of office at once instead they created an automated system to broker access to aws now anyone on the team can request access through the aws access broker repository once approved by someone through github approvals actions grants temporary access for that person to the production account accessed through g suite s saml integration into aws this helped alleviate concerns that an enterprise organization might have about a young company like zibasec we do everything we can to minimize the amount of trust we place on people and let technology grant access in a way that s well controlled documented and versioned said davila what i love about github actions is that you re not limited in your choice of tools says drake github s library of pre built actions makes it easy to integrate any tool to customize your technology ecosystem zibasec currently uses terraform and serverless framework through aws combined with actions to enable automatic deploys changes go through multiple layers of approval including several branch protection rules in github once everything is approved and merged actions kick off and deploy the changes to production managing this through github allows zibasec to maintain a thorough record of changes so they can meet the fedramp requirements without having to slow down it comes as no surprise that security is particularly important when working with federal agencies and their data zibasec uses automation and github s security features to ensure that nothing slips past their attention github advanced security runs checks on every pull request and displays the results they ve also created a tool that piggybacks off dependabot in order to facilitate their reporting needs using the github api the tool extracts vulnerability reports into a native interface so the team can clearly extract the artifacts they d need for an audit if a vulnerability is detected a github issue is opened fedramp requires that these issues be resolved and closed within a certain timeframe depending on the severity of the issue github issues provide a detailed tracking mechanism for zibasec to show fedramp auditors when a vulnerability was detected when it was addressed when the issue was opened when it was patched or discarded when the issue was closed or if it was a false positive fedramp requires a lot of documentation and any vulnerability detected by any tool is considered a legitimate finding that needs to be addressed even if the vulnerability turns out to be a false positive it would still need to be documented time consuming work that other static analysis tools haven t helped the team avoid previously zibasec had used other static analysis tools but found they generated unnecessary work due to false positives we haven t run into any false positives with advanced security said shepherd accuracy is crucial because we don t want to spend time writing documentation we want to find tools that are going to help us rather than create more work the team has saved even more time by going serverless with github enterprise cloud because zibasec doesn t run on its own data centers physical servers or machines fedramp s regulations regarding physical security don t apply to them zibasec does not have to bear the responsibility of managing and scanning server hosts with our team size it s highly unlikely that we would have been able to meet the federal requirements without a serverless model davila stated but by entrusting that process to vendors like github we have saved so many hours and dollars we haven t run into any false positives with advanced security accuracy is crucial because we don t want to spend time writing documentation we want to find tools that are going to help us rather than create more work while security and documentation are a high priority for the team they still value the importance of open source communities in a world where transparency is almost non existent they feel it s important to be as transparent as possible with end users and organizations about their use of data zibasec hosts a number of open source repositories and contributes to the community through issues as well as code contributions i think it s very valuable to practice learning and building in public said drake some organizations refrain from open source because there is some potential for security missteps but the benefits far outweigh the risks what people don t realize is that you can simultaneously be secure and open sourced with github being the de facto standard for open source communities they can trust that it will provide a secure environment for zibasec github was more than just a traditional code repository with the flexibility provided by actions and the github api they are able to function at the level of a more mature company and achieve more than would seem possible with a team of seven it s a huge accomplishment for just seven people to have gotten as far with fedramp as we have said drake github is part of our story and deserves credit for our success interested in bringing github enterprise to your organization start your free trial of github enterprise for 30 days days and increase your team s collaboration 21 per user month after trial expires curious about other plans from github explore more from github the readme project stories and voices from the developer community learn more about the readme project github copilot ai pair programmer that helps you write code faster learn more about github copilot github actions automate your workflow from idea to production learn more about github actions what will your story be start collaborating with your team on github free the basics for individuals and organizations 0 per month create a free organization team advanced collaboration for individuals and organizations 4 per month continue with team enterprise security compliance and flexible deployment 21 per month enterprise want to use github on your own check out our plans for individuals product features security team enterprise customer stories the readme project pricing resources roadmap platform developer api partners electron github desktop support docs community forum professional services skills status contact github company about blog careers press inclusion social impact shop github on twitter github on facebook github on linkedin github on youtube github on twitch github on tiktok github s organization on github 2023 github inc terms privacy updated 08 2022 site map what is git you can t perform that action at this time you signed in with another tab or window reload to refresh your session you signed out in another tab or window reload to refresh your session
Thumbnail images (randomly selected): * Images may be subject to copyright.GREEN status (no comments)
  • loading
  • Hero image for the story:...
  • zibasec1
  • zibasecgraphic
  • zibasec3
  • zibasec5
  • Twitter icon
  • Facebook icon
  • Linkedin icon
  • YouTube icon
  • Twitch icon
  • TikTok icon
  • GitHub mark

Verified site has: 71 subpage(s). Do you want to verify them? Verify pages:

1-5 6-10 11-15 16-20 21-25 26-30 31-35 36-40 41-45 46-50
51-55 56-60 61-65 66-70 71-71


The site also has references to the 2 subdomain(s)

  archive.org  Verify   help.archive.org  Verify


Top 50 hastags from of all verified websites.

Supplementary Information (add-on for SEO geeks)*- See more on header.verify-www.com

Header

HTTP/1.1 302 FOUND
Server nginx
Date Sat, 26 Sep 2026 23:21:14 GMT
Content-Type text/plain; charset=utf-8
Content-Length 0
Connection close
x-archive-redirect-reason found capture at 20230202224029
location htt???/web.archive.org/web/20230202224029/htt????/github.com/customer-stories/zibasec
server-timing captures_list;dur=0.539843, exclusion.robots;dur=0.068686, exclusion.robots.policy;dur=0.058750, esindex;dur=0.007201, cdx.remote;dur=11.189452, LoadShardBlock;dur=942.237018, PetaboxLoader3.datanode;dur=114.499802, PetaboxLoader3.resolve;dur=62.213527
x-app-server wwwb-app249-dc8
x-ts 302
x-tr 984
server-timing TR;dur=0,Tw;dur=0,Tc;dur=1
set-cookie wb-p-SERVER=wwwb-app249; path=/
X-location All
X-AS 16276
X-RL 0
X-NA 0
X-Page-Cache MISS
Server-Timing MISS
X-NID OVH SAS
Referrer-Policy no-referrer-when-downgrade
Permissions-Policy interest-cohort=()
X-sd 0
HTTP/1.1 200 OK
Server nginx
Date Sat, 26 Sep 2026 23:21:14 GMT
Content-Type text/html; charset=utf-8
Transfer-Encoding chunked
Connection close
x-archive-orig-server GitHub.com
x-archive-orig-date Thu, 02 Feb 2023 22:40:30 GMT
x-archive-orig-vary X-PJAX, X-PJAX-Container, Turbo-Visit, Turbo-Frame, Accept-Encoding, Accept, X-Requested-With
x-archive-orig-etag W/ 64e2aa804eea4c62a3fd15c455de9838
x-archive-orig-cache-control max-age=0, private, must-revalidate
x-archive-orig-strict-transport-security max-age=31536000; includeSubdomains; preload
x-archive-orig-x-frame-options deny
x-archive-orig-x-content-type-options nosniff
x-archive-orig-x-xss-protection 0
x-archive-orig-referrer-policy origin-when-cross-origin, strict-origin-when-cross-origin
x-archive-orig-content-security-policy default-src none ; base-uri self ; block-all-mixed-content; child-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/; connect-src self uploads.github.com objects-origin.githubusercontent.com www.githubstatus.com collector.github.com raw.githubusercontent.com api.github.com github-cloud.s3.amazonaws.com github-production-repository-file-5c1aeb.s3.amazonaws.com github-production-upload-manifest-file-7fdce7.s3.amazonaws.com github-production-user-asset-6210df.s3.amazonaws.com cdn.optimizely.com logx.optimizely.com/v1/events *.actions.githubusercontent.com wss://*.actions.githubusercontent.com online.visualstudio.com/api/v1/locations github-production-repository-image-32fea6.s3.amazonaws.com github-production-release-asset-2e65be.s3.amazonaws.com insights.github.com wss://alive.github.com; font-src github.githubassets.com; form-action self github.com gist.github.com objects-origin.githubusercontent.com; frame-ancestors none ; frame-src viewscreen.githubusercontent.com notebooks.githubusercontent.com; img-src self data: github.githubassets.com media.githubusercontent.com camo.githubusercontent.com identicons.github.com avatars.githubusercontent.com github-cloud.s3.amazonaws.com objects.githubusercontent.com objects-origin.githubusercontent.com secured-user-images.githubusercontent.com/ opengraph.githubassets.com github-production-user-asset-6210df.s3.amazonaws.com customer-stories-feed.github.com spotlights-feed.github.com *.githubusercontent.com images.ctfassets.net/aukesvz1i7g8/; manifest-src self ; media-src github.com user-images.githubusercontent.com/ secured-user-images.githubusercontent.com/; script-src github.githubassets.com; style-src unsafe-inline github.githubassets.com; worker-src github.com/assets-cdn/worker/ gist.github.com/assets-cdn/worker/
x-archive-orig-accept-ranges bytes
x-archive-orig-x-github-request-id C4BC:7C88:570453:816526:63DC3BDD
x-archive-orig-connection close
x-archive-guessed-content-type text/html
x-archive-guessed-charset utf-8
memento-datetime Thu, 02 Feb 2023 22:40:29 GMT
link <htt????/github.com/customer-stories/zibasec>; rel= original , <htt???/web.archive.org/web/timemap/link/htt????/github.com/customer-stories/zibasec>; rel= timemap ; type= application/link-format , <htt???/web.archive.org/web/htt????/github.com/customer-stories/zibasec>; rel= timegate , <htt???/web.archive.org/web/20200916234813/htt????/github.com/customer-stories/zibasec>; rel= first memento ; datetime= Wed, 16 Sep 2020 23:48:13 GMT , <htt???/web.archive.org/web/20230130232406/htt????/github.com/customer-stories/zibasec>; rel= prev memento ; datetime= Mon, 30 Jan 2023 23:24:06 GMT , <htt???/web.archive.org/web/20230202224029/htt????/github.com/customer-stories/zibasec>; rel= memento ; datetime= Thu, 02 Feb 2023 22:40:29 GMT , <htt???/web.archive.org/web/20230205002714/htt????/github.com/customer-stories/zibasec>; rel= next memento ; datetime= Sun, 05 Feb 2023 00:27:14 GMT , <htt???/web.archive.org/web/20260922043750/htt????/github.com/customer-stories/zibasec>; rel= last memento ; datetime= Tue, 22 Sep 2026 04:37:50 GMT
content-security-policy default-src self unsafe-eval unsafe-inline data: blob: archive.org web.archive.org web-static.archive.org wayback-api.archive.org athena.archive.org analytics.archive.org pragma.archivelab.org wwwb-events.archive.org
x-archive-src github.com-20230202-103537/IA-FOC-github.com-20230202220308-00000.warc.gz
server-timing captures_list;dur=0.727408, exclusion.robots;dur=0.069601, exclusion.robots.policy;dur=0.054908, esindex;dur=0.009448, cdx.remote;dur=13.463348, LoadShardBlock;dur=208.845926, PetaboxLoader3.datanode;dur=131.588306, PetaboxLoader3.resolve;dur=105.966743, load_resource;dur=82.615202, nav;dur=0.296322
x-app-server wwwb-app54-dc6
x-ts 200
x-tr 437
server-timing TR;dur=0,Tw;dur=0,Tc;dur=0
set-cookie wb-p-SERVER=wwwb-app54; path=/
X-location All
X-AS 16276
X-RL 0
X-NA 0
X-Page-Cache MISS
Server-Timing MISS
X-NID OVH SAS
Referrer-Policy no-referrer-when-downgrade
Permissions-Policy interest-cohort=()
X-sd 0
Content-Encoding gzip

Meta Tags

title="ZibaSec · GitHub"
charset="utf-8"
name="request-id" content="C4BC:7C88:570453:816526:63DC3BDD" data-pjax-transient="true"
name="html-safe-nonce" content="d82eabaa87b09e6772dbc8b8eba04485c94802f29b2c591d5e7cd76eeb1ee73c" data-pjax-transient="true"
name="visitor-payload" content="eyJyZWZlcnJlciI6Imh0dHBzOi8vZ2l0aHViLmNvbS9jdXN0b21lci1zdG9yaWVzIiwicmVxdWVzdF9pZCI6IkM0QkM6N0M4ODo1NzA0NTM6ODE2NTI2OjYzREMzQkREIiwidmlzaXRvcl9pZCI6IjkxMDA2ODQwNjQzMzY5MTcyODAiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ==" data-pjax-transient="true"
name="visitor-hmac" content="a59340f60832439b1ad9de5a8f68e77ec710c8389a2d7860bf2b64350bdae2fc" data-pjax-transient="true"
name="github-keyboard-shortcuts" content="" data-turbo-transient="true"
name="selected-link" value="/customer-stories" data-turbo-transient
name="google-site-verification" content="c1kuD-K2HIVF635lypcsWPoD4kilo5-jA_wBFyT4uMY"
name="google-site-verification" content="KT5gs8h0wvaagLKAVWq8bbeNwnZZK1r1XQysX3xurLU"
name="google-site-verification" content="ZzhVyEFwb7w3e0-uOTltm8Jsck2F5StVihD0exw2fsA"
name="google-site-verification" content="GXs5KoUUkNCoaAZn7wPN-t01Pywp9M3sEjnt_3_ZWPc"
name="google-site-verification" content="Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I"
name="octolytics-url" content="htt????/collector.github.com/github/collect"
name="user-login" content=""
name="viewport" content="width=device-width"
name="description" content="ZibaSec achieves great feats with a small team to protect federal organizations from phishing attacks."
property="fb:app_id" content="1401488693436528"
name="apple-itunes-app" content="app-id=1477376905"
name="twitter:image:src" content="//images.ctfassets.net/aukesvz1i7g8/1Zi2RGTOfsUfoGZnRvGTT5/7686a9d216a32e7ae071a08205017431/zibasechero.jpg"
name="twitter:site" content="@github"
name="twitter:card" content="summary_large_image"
name="twitter:title" content="How ZibaSec uses GitHub"
name="twitter:description" content="ZibaSec achieves great feats with a small team to protect federal organizations from phishing attacks."
property="og:image" content="//web.archive.org/web/20230202224029im_/htt????/images.ctfassets.net/aukesvz1i7g8/1Zi2RGTOfsUfoGZnRvGTT5/7686a9d216a32e7ae071a08205017431/zibasechero.jpg"
property="og:image:alt" content="ZibaSec achieves great feats with a small team to protect federal organizations from phishing attacks."
property="og:site_name" content="GitHub"
property="og:type" content="object"
property="og:title" content="How ZibaSec uses GitHub"
property="og:url" content="htt???/web.archive.org/web/20230202224029/htt????/github.com/customer-stories/zibasec"
property="og:description" content="ZibaSec achieves great feats with a small team to protect federal organizations from phishing attacks."
name="hostname" content="github.com"
name="expected-hostname" content="github.com"
name="enabled-features" content="TURBO_EXPERIMENT_RISKY,IMAGE_METRIC_TRACKING,GEOJSON_AZURE_MAPS"
http-equiv="x-pjax-version" content="b55c2d5def9b44475a286d209c6f452a1202a429887c15563848762f3b0cf867" data-turbo-track="reload"
http-equiv="x-pjax-csp-version" content="2863783a51f92c8de8712585ab173a82cc854c99811e59d634698a36984acb55" data-turbo-track="reload"
http-equiv="x-pjax-css-version" content="cd753f253ddc9585038376b112bb27a033ce85a91d16b2f73ed8700e7f404269" data-turbo-track="reload"
http-equiv="x-pjax-js-version" content="3670defaf0d45be1df11b585a7bd3fc44fb813030227133e6be11e086e754b41" data-turbo-track="reload"
name="turbo-cache-control" content="no-preview" data-turbo-transient=""
name="is_logged_out_page" content="true"
name="turbo-body-classes" content="logged-out env-production page-responsive f4"
name="browser-stats-url" content="htt????/api.github.com/_private/browser/stats"
name="browser-errors-url" content="htt????/api.github.com/_private/browser/errors"
name="browser-optimizely-client-errors-url" content="htt????/api.github.com/_private/browser/optimizely_client/errors"
name="theme-color" content="#1e2327"

Load Info

page size32344
load time (s)2.173817
redirect count1
speed download14884
server IP 207.241.237.3
* all occurrences of the string "http://" have been changed to "htt???/"