[{"data":1,"prerenderedAt":989},["ShallowReactive",2],{"docs-pages":3,"docs-\u002Fdocs\u002Freference\u002Ffaq\u002F":960},[4,98,243,337,416,468,534,599,655,698,780,845,893],{"id":5,"title":6,"body":7,"description":90,"extension":91,"meta":92,"navigation":93,"path":94,"seo":95,"stem":96,"__hash__":97},"docs\u002Fdocs\u002F1.getting-started\u002F1.introduction.md","Introduction",{"type":8,"value":9,"toc":78},"minimark",[10,14,18,23,39,43,48,51,55,58,62,65,69],[11,12,6],"h1",{"id":13},"introduction",[15,16,17],"p",{},"Bitfy is File Integrity Monitoring for critical files, configs, binaries, and certificates. It establishes approved baselines, detects unauthorized change in real time, and keeps immutable evidence for investigations and audits.",[19,20,22],"h2",{"id":21},"what-bitfy-monitors","What Bitfy monitors",[24,25,26,30,33,36],"ul",{},[27,28,29],"li",{},"File content hashes and metadata",[27,31,32],{},"Permission and ownership drift",[27,34,35],{},"Creates, edits, deletes, and renames on scoped paths",[27,37,38],{},"Host coverage across servers, VMs, and container hosts",[19,40,42],{"id":41},"core-concepts","Core concepts",[44,45,47],"h3",{"id":46},"baselines","Baselines",[15,49,50],{},"A baseline is a known-good snapshot of scoped paths. Once approved, Bitfy compares every subsequent change against that state.",[44,52,54],{"id":53},"change-feed","Change feed",[15,56,57],{},"The change feed lists integrity events with context — what changed, when it changed, and whether the change was expected.",[44,59,61],{"id":60},"evidence","Evidence",[15,63,64],{},"Bitfy retains immutable event history so teams can export auditor-ready FIM reports for frameworks such as PCI DSS, SOC 2, ISO 27001, and HIPAA.",[19,66,68],{"id":67},"next-steps","Next steps",[15,70,71,72,77],{},"Continue with ",[73,74,76],"a",{"href":75},"\u002Fdocs\u002Fgetting-started\u002Finstallation\u002F","Installation"," to deploy your first agent.",{"title":79,"searchDepth":80,"depth":80,"links":81},"",2,[82,83,89],{"id":21,"depth":80,"text":22},{"id":41,"depth":80,"text":42,"children":84},[85,87,88],{"id":46,"depth":86,"text":47},3,{"id":53,"depth":86,"text":54},{"id":60,"depth":86,"text":61},{"id":67,"depth":80,"text":68},"What Bitfy File Integrity Monitoring covers and how the control model works.","md",{},true,"\u002Fdocs\u002Fgetting-started\u002Fintroduction",{"title":6,"description":90},"docs\u002F1.getting-started\u002F1.introduction","XHFeITYkxfKYhUjNRqt44b7NzugN2H0xKN86AeBAsBs",{"id":99,"title":76,"body":100,"description":237,"extension":91,"meta":238,"navigation":93,"path":239,"seo":240,"stem":241,"__hash__":242},"docs\u002Fdocs\u002F1.getting-started\u002F2.installation.md",{"type":8,"value":101,"toc":231},[102,105,108,112,123,127,151,199,203,206,217,219,227],[11,103,76],{"id":104},"installation",[15,106,107],{},"Install a Bitfy agent on each host you want to monitor. Agents are lightweight, watch scoped paths, and stream integrity events to your Bitfy workspace.",[19,109,111],{"id":110},"requirements","Requirements",[24,113,114,117,120],{},[27,115,116],{},"Linux, Windows Server, or container host with outbound HTTPS",[27,118,119],{},"Ability to install a system service or daemon",[27,121,122],{},"Network access to your Bitfy control plane",[19,124,126],{"id":125},"install-the-agent","Install the agent",[128,129,130,138,141,144],"ol",{},[27,131,132,133,137],{},"Sign in to Bitfy and open ",[134,135,136],"strong",{},"Hosts → Add host",".",[27,139,140],{},"Copy the install command for your operating system.",[27,142,143],{},"Run the command with sufficient privileges to create a service.",[27,145,146,147,150],{},"Confirm the host appears as ",[134,148,149],{},"Online"," in the dashboard.",[152,153,157],"pre",{"className":154,"code":155,"language":156,"meta":79,"style":79},"language-bash shiki shiki-themes github-dark","curl -fsSL https:\u002F\u002Fget.bitfy.dev\u002Finstall.sh | sudo bash -s -- --token YOUR_TOKEN\n","bash",[158,159,160],"code",{"__ignoreMap":79},[161,162,165,169,173,177,181,184,187,190,193,196],"span",{"class":163,"line":164},"line",1,[161,166,168],{"class":167},"svObZ","curl",[161,170,172],{"class":171},"sDLfK"," -fsSL",[161,174,176],{"class":175},"sU2Wk"," https:\u002F\u002Fget.bitfy.dev\u002Finstall.sh",[161,178,180],{"class":179},"snl16"," |",[161,182,183],{"class":167}," sudo",[161,185,186],{"class":175}," bash",[161,188,189],{"class":171}," -s",[161,191,192],{"class":171}," --",[161,194,195],{"class":171}," --token",[161,197,198],{"class":175}," YOUR_TOKEN\n",[19,200,202],{"id":201},"verify-connectivity","Verify connectivity",[15,204,205],{},"After install, the agent registers the host and begins heartbeats. If the host stays offline:",[24,207,208,211,214],{},[27,209,210],{},"Confirm outbound HTTPS is allowed",[27,212,213],{},"Check the agent service status",[27,215,216],{},"Re-run registration with a fresh token",[19,218,68],{"id":67},[15,220,221,222,226],{},"Move on to ",[73,223,225],{"href":224},"\u002Fdocs\u002Fgetting-started\u002Fquickstart\u002F","Quickstart"," to scope paths and approve a baseline.",[228,229,230],"style",{},"html pre.shiki code .svObZ, html code.shiki .svObZ{--shiki-default:#B392F0}html pre.shiki code .sDLfK, html code.shiki .sDLfK{--shiki-default:#79B8FF}html pre.shiki code .sU2Wk, html code.shiki .sU2Wk{--shiki-default:#9ECBFF}html pre.shiki code .snl16, html code.shiki .snl16{--shiki-default:#F97583}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":79,"searchDepth":80,"depth":80,"links":232},[233,234,235,236],{"id":110,"depth":80,"text":111},{"id":125,"depth":80,"text":126},{"id":201,"depth":80,"text":202},{"id":67,"depth":80,"text":68},"Install the Bitfy agent and connect your first host.",{},"\u002Fdocs\u002Fgetting-started\u002Finstallation",{"title":76,"description":237},"docs\u002F1.getting-started\u002F2.installation","50_J76-RgdsqSJCW6tes5WE_2DOUWwqnc9-INWVGPCU",{"id":244,"title":225,"body":245,"description":331,"extension":91,"meta":332,"navigation":93,"path":333,"seo":334,"stem":335,"__hash__":336},"docs\u002Fdocs\u002F1.getting-started\u002F3.quickstart.md",{"type":8,"value":246,"toc":325},[247,250,253,257,264,278,281,285,288,292,295,306,310,317],[11,248,225],{"id":249},"quickstart",[15,251,252],{},"Get from a connected host to live File Integrity Monitoring in a few minutes.",[19,254,256],{"id":255},"_1-scope-critical-paths","1. Scope critical paths",[15,258,259,260,263],{},"Open ",[134,261,262],{},"Baselines → New policy"," and add the paths that matter most:",[24,265,266,269,272,275],{},[27,267,268],{},"System binaries and shared libraries",[27,270,271],{},"Application configs and secrets mounts",[27,273,274],{},"Web roots and deployment artifacts",[27,276,277],{},"Certificate and key directories",[15,279,280],{},"Start narrow. Expand coverage after alerts are tuned.",[19,282,284],{"id":283},"_2-capture-and-approve-a-baseline","2. Capture and approve a baseline",[15,286,287],{},"Run an initial scan, review the inventory, then approve the known-good state. Bitfy only treats later differences as integrity events once a baseline is approved.",[19,289,291],{"id":290},"_3-confirm-alert-delivery","3. Confirm alert delivery",[15,293,294],{},"Send a controlled test change to a scoped file and verify:",[24,296,297,300,303],{},[27,298,299],{},"The event appears in the change feed",[27,301,302],{},"Severity and path context look correct",[27,304,305],{},"Notifications reach your preferred channel",[19,307,309],{"id":308},"_4-export-evidence","4. Export evidence",[15,311,312,313,316],{},"From ",[134,314,315],{},"Compliance",", generate a sample FIM evidence pack to confirm reporting works for your audit workflow.",[15,318,319,320,324],{},"You are ready for production monitoring. Continue with ",[73,321,323],{"href":322},"\u002Fdocs\u002Fconfiguration\u002Fagents\u002F","Agents"," for host-scale configuration.",{"title":79,"searchDepth":80,"depth":80,"links":326},[327,328,329,330],{"id":255,"depth":80,"text":256},{"id":283,"depth":80,"text":284},{"id":290,"depth":80,"text":291},{"id":308,"depth":80,"text":309},"Scope critical paths, approve a baseline, and receive your first integrity alert.",{},"\u002Fdocs\u002Fgetting-started\u002Fquickstart",{"title":225,"description":331},"docs\u002F1.getting-started\u002F3.quickstart","5WI2iZjfGOVXABw7J1RT7wj72ms9S3dsm609pwoXMdc",{"id":338,"title":323,"body":339,"description":410,"extension":91,"meta":411,"navigation":93,"path":412,"seo":413,"stem":414,"__hash__":415},"docs\u002Fdocs\u002F2.configuration\u002F1.agents.md",{"type":8,"value":340,"toc":405},[341,344,347,351,354,368,372,379,398,402],[11,342,323],{"id":343},"agents",[15,345,346],{},"Agents collect integrity signals on each host and send them to Bitfy. Keep agents online, grouped by environment, and updated with your rollout process.",[19,348,350],{"id":349},"host-groups","Host groups",[15,352,353],{},"Use host groups to apply shared path policies across similar systems:",[24,355,356,359,362,365],{},[27,357,358],{},"Production app servers",[27,360,361],{},"Jump hosts and bastions",[27,363,364],{},"Container worker nodes",[27,366,367],{},"Database servers",[19,369,371],{"id":370},"agent-health","Agent health",[15,373,374,375,378],{},"Monitor agent status from ",[134,376,377],{},"Hosts",":",[24,380,381,386,392],{},[27,382,383,385],{},[134,384,149],{}," — heartbeats are current",[27,387,388,391],{},[134,389,390],{},"Degraded"," — delayed scans or partial reporting",[27,393,394,397],{},[134,395,396],{},"Offline"," — no recent heartbeat",[19,399,401],{"id":400},"upgrades","Upgrades",[15,403,404],{},"Roll agent updates in stages. Validate on a canary group before production fleets.",{"title":79,"searchDepth":80,"depth":80,"links":406},[407,408,409],{"id":349,"depth":80,"text":350},{"id":370,"depth":80,"text":371},{"id":400,"depth":80,"text":401},"Manage Bitfy agents, host groups, and coverage.",{},"\u002Fdocs\u002Fconfiguration\u002Fagents",{"title":323,"description":410},"docs\u002F2.configuration\u002F1.agents","e_fb04rFCWbvIdoNif8af2buouu0mgONiaYu--PThLk",{"id":417,"title":47,"body":418,"description":462,"extension":91,"meta":463,"navigation":93,"path":464,"seo":465,"stem":466,"__hash__":467},"docs\u002Fdocs\u002F2.configuration\u002F2.baselines.md",{"type":8,"value":419,"toc":457},[420,422,425,429,443,447,450,454],[11,421,47],{"id":46},[15,423,424],{},"Baselines define the trusted state for scoped paths. Strong baseline hygiene is the difference between high-signal alerts and noisy change feeds.",[19,426,428],{"id":427},"create-a-baseline-policy","Create a baseline policy",[128,430,431,434,437,440],{},[27,432,433],{},"Choose target hosts or groups.",[27,435,436],{},"Define include and exclude path patterns.",[27,438,439],{},"Run an inventory scan.",[27,441,442],{},"Review unexpected files before approval.",[19,444,446],{"id":445},"approval-workflow","Approval workflow",[15,448,449],{},"Require dual control for production baselines. Capture who approved the change and why, then keep that context attached to future drift events.",[19,451,453],{"id":452},"re-baselining","Re-baselining",[15,455,456],{},"Schedule or manually refresh baselines after planned releases. Correlate re-baseline windows with change tickets so intentional updates do not open incidents.",{"title":79,"searchDepth":80,"depth":80,"links":458},[459,460,461],{"id":427,"depth":80,"text":428},{"id":445,"depth":80,"text":446},{"id":452,"depth":80,"text":453},"Create, approve, and refresh known-good integrity baselines.",{},"\u002Fdocs\u002Fconfiguration\u002Fbaselines",{"title":47,"description":462},"docs\u002F2.configuration\u002F2.baselines","bcW016QsDJpCJMoTMgU3845PV7rSMQaoEoqcD7CiPz4",{"id":469,"title":470,"body":471,"description":528,"extension":91,"meta":529,"navigation":93,"path":530,"seo":531,"stem":532,"__hash__":533},"docs\u002Fdocs\u002F2.configuration\u002F3.alerts.md","Alerts",{"type":8,"value":472,"toc":523},[473,476,479,483,509,513,516,520],[11,474,470],{"id":475},"alerts",[15,477,478],{},"Bitfy alerts when monitored paths drift from an approved baseline. Tune severity, suppression, and destinations so responders get actionable signals.",[19,480,482],{"id":481},"severity","Severity",[24,484,485,491,497,503],{},[27,486,487,490],{},[134,488,489],{},"Critical"," — unauthorized binary or credential path changes",[27,492,493,496],{},[134,494,495],{},"High"," — unexpected config or permission drift",[27,498,499,502],{},[134,500,501],{},"Medium"," — lower-risk path activity that still needs review",[27,504,505,508],{},[134,506,507],{},"Info"," — approved or low-priority events for audit context",[19,510,512],{"id":511},"destinations","Destinations",[15,514,515],{},"Send alerts to email, webhook, SIEM, or chat ops tools. Map destinations by host group so the right team owns the response.",[19,517,519],{"id":518},"noise-reduction","Noise reduction",[15,521,522],{},"Suppress known maintenance windows, ignore volatile temp paths, and require consecutive observations for flapping files before paging.",{"title":79,"searchDepth":80,"depth":80,"links":524},[525,526,527],{"id":481,"depth":80,"text":482},{"id":511,"depth":80,"text":512},{"id":518,"depth":80,"text":519},"Route integrity events to the right responders with less noise.",{},"\u002Fdocs\u002Fconfiguration\u002Falerts",{"title":470,"description":528},"docs\u002F2.configuration\u002F3.alerts","Pzr_st7s1pMvg28hTegTiUaEa-krTb0fLNwMVpQJwd4",{"id":535,"title":536,"body":537,"description":593,"extension":91,"meta":594,"navigation":93,"path":595,"seo":596,"stem":597,"__hash__":598},"docs\u002Fdocs\u002F3.guides\u002F1.monitoring-paths.md","Monitoring paths",{"type":8,"value":538,"toc":588},[539,542,545,549,566,570,581,585],[11,540,536],{"id":541},"monitoring-paths",[15,543,544],{},"Good path scoping keeps FIM useful. Monitor what proves integrity and skip directories that change constantly by design.",[19,546,548],{"id":547},"high-value-targets","High-value targets",[24,550,551,554,557,560,563],{},[27,552,553],{},"Package-managed binaries",[27,555,556],{},"Service unit files and init configs",[27,558,559],{},"Application config roots",[27,561,562],{},"TLS certificates and private keys",[27,564,565],{},"Cron, sudoers, and auth policy files",[19,567,569],{"id":568},"paths-to-exclude-carefully","Paths to exclude carefully",[24,571,572,575,578],{},[27,573,574],{},"Logs and spool directories",[27,576,577],{},"Caches and temporary build output",[27,579,580],{},"Highly dynamic runtime state, unless you have a compliance reason",[19,582,584],{"id":583},"pattern-tips","Pattern tips",[15,586,587],{},"Prefer explicit paths over broad wildcards. When using globs, pair includes with excludes so one noisy subtree does not dominate the feed.",{"title":79,"searchDepth":80,"depth":80,"links":589},[590,591,592],{"id":547,"depth":80,"text":548},{"id":568,"depth":80,"text":569},{"id":583,"depth":80,"text":584},"Choose high-value paths and avoid noisy coverage.",{},"\u002Fdocs\u002Fguides\u002Fmonitoring-paths",{"title":536,"description":593},"docs\u002F3.guides\u002F1.monitoring-paths","TRcRsvQRtFXw2VhjzymDBBgdfc5AejNfFizodBF3aYA",{"id":600,"title":601,"body":602,"description":649,"extension":91,"meta":650,"navigation":93,"path":651,"seo":652,"stem":653,"__hash__":654},"docs\u002Fdocs\u002F3.guides\u002F2.compliance-evidence.md","Compliance evidence",{"type":8,"value":603,"toc":644},[604,607,610,614,628,632,637,641],[11,605,601],{"id":606},"compliance-evidence",[15,608,609],{},"Bitfy helps produce continuous File Integrity Monitoring evidence for PCI DSS, SOC 2, ISO 27001, HIPAA, and internal control programs.",[19,611,613],{"id":612},"what-auditors-usually-ask-for","What auditors usually ask for",[24,615,616,619,622,625],{},[27,617,618],{},"Which critical files are monitored",[27,620,621],{},"When baselines were approved",[27,623,624],{},"What unauthorized changes occurred",[27,626,627],{},"Who reviewed or remediated each event",[19,629,631],{"id":630},"exporting-reports","Exporting reports",[15,633,312,634,636],{},[134,635,315],{},", select the period, hosts, and framework mapping, then export a pack that includes inventory, change history, and approval records.",[19,638,640],{"id":639},"continuous-vs-point-in-time","Continuous vs point-in-time",[15,642,643],{},"Point-in-time checksums go stale quickly. Continuous monitoring with retained history better demonstrates ongoing control effectiveness.",{"title":79,"searchDepth":80,"depth":80,"links":645},[646,647,648],{"id":612,"depth":80,"text":613},{"id":630,"depth":80,"text":631},{"id":639,"depth":80,"text":640},"Export continuous FIM evidence for common audit frameworks.",{},"\u002Fdocs\u002Fguides\u002Fcompliance-evidence",{"title":601,"description":649},"docs\u002F3.guides\u002F2.compliance-evidence","opcBeWFjezITohcg96YEpWrZeh7w3byU4cShwJDMcNM",{"id":656,"title":657,"body":658,"description":692,"extension":91,"meta":693,"navigation":93,"path":694,"seo":695,"stem":696,"__hash__":697},"docs\u002Fdocs\u002F3.guides\u002F3.integrations.md","Integrations",{"type":8,"value":659,"toc":687},[660,663,666,670,673,677,680,684],[11,661,657],{"id":662},"integrations",[15,664,665],{},"Connect Bitfy to the tools your security and platform teams already use.",[19,667,669],{"id":668},"siem-and-webhooks","SIEM and webhooks",[15,671,672],{},"Forward integrity events as structured JSON to your SIEM or automation platform. Include host, path, hash diff summary, and severity.",[19,674,676],{"id":675},"identity","Identity",[15,678,679],{},"Use SSO for operator access and map roles to baseline approval permissions.",[19,681,683],{"id":682},"ticketing","Ticketing",[15,685,686],{},"Optionally attach change ticket IDs when approving re-baselines so investigations can separate planned work from unauthorized drift.",{"title":79,"searchDepth":80,"depth":80,"links":688},[689,690,691],{"id":668,"depth":80,"text":669},{"id":675,"depth":80,"text":676},{"id":682,"depth":80,"text":683},"Connect Bitfy to SIEM, webhooks, and identity providers.",{},"\u002Fdocs\u002Fguides\u002Fintegrations",{"title":657,"description":692},"docs\u002F3.guides\u002F3.integrations","xt4Thy3qdk0qFQRw_J7sAK4YXCaB_AAZPPNPBxDW5J4",{"id":699,"title":700,"body":701,"description":774,"extension":91,"meta":775,"navigation":93,"path":776,"seo":777,"stem":778,"__hash__":779},"docs\u002Fdocs\u002F4.reference\u002F1.cli.md","CLI",{"type":8,"value":702,"toc":770},[703,706,709,713,757,761,767],[11,704,700],{"id":705},"cli",[15,707,708],{},"Use the Bitfy CLI for install helpers, local diagnostics, and scripted baseline operations.",[19,710,712],{"id":711},"common-commands","Common commands",[152,714,716],{"className":154,"code":715,"language":156,"meta":79,"style":79},"bitfy status\nbitfy paths list\nbitfy scan --policy production-core\nbitfy doctor\n",[158,717,718,726,736,749],{"__ignoreMap":79},[161,719,720,723],{"class":163,"line":164},[161,721,722],{"class":167},"bitfy",[161,724,725],{"class":175}," status\n",[161,727,728,730,733],{"class":163,"line":80},[161,729,722],{"class":167},[161,731,732],{"class":175}," paths",[161,734,735],{"class":175}," list\n",[161,737,738,740,743,746],{"class":163,"line":86},[161,739,722],{"class":167},[161,741,742],{"class":175}," scan",[161,744,745],{"class":171}," --policy",[161,747,748],{"class":175}," production-core\n",[161,750,752,754],{"class":163,"line":751},4,[161,753,722],{"class":167},[161,755,756],{"class":175}," doctor\n",[19,758,760],{"id":759},"diagnostics","Diagnostics",[15,762,763,766],{},[158,764,765],{},"bitfy doctor"," checks service health, token validity, and outbound connectivity. Include its output when opening a support case.",[228,768,769],{},"html pre.shiki code .svObZ, html code.shiki .svObZ{--shiki-default:#B392F0}html pre.shiki code .sU2Wk, html code.shiki .sU2Wk{--shiki-default:#9ECBFF}html pre.shiki code .sDLfK, html code.shiki .sDLfK{--shiki-default:#79B8FF}html .default .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}html .shiki span {color: var(--shiki-default);background: var(--shiki-default-bg);font-style: var(--shiki-default-font-style);font-weight: var(--shiki-default-font-weight);text-decoration: var(--shiki-default-text-decoration);}",{"title":79,"searchDepth":80,"depth":80,"links":771},[772,773],{"id":711,"depth":80,"text":712},{"id":759,"depth":80,"text":760},"Common Bitfy CLI commands for agents and local diagnostics.",{},"\u002Fdocs\u002Freference\u002Fcli",{"title":700,"description":774},"docs\u002F4.reference\u002F1.cli","vWobPeyDexR6gijN7ac-gllDxpLxOqXWxh3k-QBMyrM",{"id":781,"title":782,"body":783,"description":839,"extension":91,"meta":840,"navigation":93,"path":841,"seo":842,"stem":843,"__hash__":844},"docs\u002Fdocs\u002F4.reference\u002F2.api.md","API",{"type":8,"value":784,"toc":835},[785,788,791,795,798,802,828],[11,786,782],{"id":787},"api",[15,789,790],{},"The Bitfy API lets you automate host inventory, policy assignment, and evidence export.",[19,792,794],{"id":793},"authentication","Authentication",[15,796,797],{},"Authenticate with a workspace API token over HTTPS. Rotate tokens regularly and scope them to least privilege.",[19,799,801],{"id":800},"core-resources","Core resources",[24,803,804,810,816,822],{},[27,805,806,809],{},[158,807,808],{},"\u002Fhosts"," — inventory and agent health",[27,811,812,815],{},[158,813,814],{},"\u002Fpolicies"," — path policies and baseline state",[27,817,818,821],{},[158,819,820],{},"\u002Fevents"," — integrity change feed",[27,823,824,827],{},[158,825,826],{},"\u002Fexports"," — compliance evidence jobs",[15,829,830,831,834],{},"See your workspace ",[134,832,833],{},"Settings → API"," for endpoint details and examples.",{"title":79,"searchDepth":80,"depth":80,"links":836},[837,838],{"id":793,"depth":80,"text":794},{"id":800,"depth":80,"text":801},"Overview of Bitfy REST API resources for automation.",{},"\u002Fdocs\u002Freference\u002Fapi",{"title":782,"description":839},"docs\u002F4.reference\u002F2.api","usiVAgZZoKIqnUHUR1nx9k2j9v1ThzI3FLFuPSyydU4",{"id":846,"title":847,"body":848,"description":887,"extension":91,"meta":888,"navigation":93,"path":889,"seo":890,"stem":891,"__hash__":892},"docs\u002Fdocs\u002F4.reference\u002F3.faq.md","FAQ",{"type":8,"value":849,"toc":881},[850,853,857,860,864,867,871,874,878],[11,851,847],{"id":852},"faq",[19,854,856],{"id":855},"how-quickly-can-i-get-started","How quickly can I get started?",[15,858,859],{},"Install an agent, define critical paths, approve a baseline, and start receiving integrity alerts within minutes.",[19,861,863],{"id":862},"does-bitfy-replace-antivirus","Does Bitfy replace antivirus?",[15,865,866],{},"No. Bitfy focuses on File Integrity Monitoring — proving what changed on critical paths — and complements endpoint protection and detection tools.",[19,868,870],{"id":869},"can-i-start-small","Can I start small?",[15,872,873],{},"Yes. Begin with a focused set of paths and expand coverage as your environment and compliance needs grow.",[19,875,877],{"id":876},"which-frameworks-does-bitfy-support","Which frameworks does Bitfy support?",[15,879,880],{},"Bitfy helps produce FIM evidence commonly requested for PCI DSS, SOC 2, ISO 27001, HIPAA, and related controls.",{"title":79,"searchDepth":80,"depth":80,"links":882},[883,884,885,886],{"id":855,"depth":80,"text":856},{"id":862,"depth":80,"text":863},{"id":869,"depth":80,"text":870},{"id":876,"depth":80,"text":877},"Answers to common Bitfy documentation questions.",{},"\u002Fdocs\u002Freference\u002Ffaq",{"title":847,"description":887},"docs\u002F4.reference\u002F3.faq","R61VCTQ-n1qX_qhFukDV6NGot_gQwzHd_8x7vmwFpyY",{"id":894,"title":895,"body":896,"description":954,"extension":91,"meta":955,"navigation":93,"path":956,"seo":957,"stem":958,"__hash__":959},"docs\u002Fdocs\u002Findex.md","Documentation",{"type":8,"value":897,"toc":950},[898,901,904,908,926,930],[11,899,895],{"id":900},"documentation",[15,902,903],{},"Welcome to the Bitfy docs. Use these guides to install agents, approve baselines, and produce compliance-ready File Integrity Monitoring evidence.",[19,905,907],{"id":906},"start-here","Start here",[24,909,910,916,921],{},[27,911,912,915],{},[73,913,6],{"href":914},"\u002Fdocs\u002Fgetting-started\u002Fintroduction\u002F"," — what Bitfy monitors and why it matters",[27,917,918,920],{},[73,919,76],{"href":75}," — install an agent on your first host",[27,922,923,925],{},[73,924,225],{"href":224}," — baseline a path and receive your first alert",[19,927,929],{"id":928},"explore-by-topic","Explore by topic",[24,931,932,938,944],{},[27,933,934,937],{},[134,935,936],{},"Configuration"," — agents, baselines, and alert routing",[27,939,940,943],{},[134,941,942],{},"Guides"," — path scoping, compliance evidence, and integrations",[27,945,946,949],{},[134,947,948],{},"Reference"," — CLI, API, and FAQ",{"title":79,"searchDepth":80,"depth":80,"links":951},[952,953],{"id":906,"depth":80,"text":907},{"id":928,"depth":80,"text":929},"Learn how to install, configure, and operate Bitfy File Integrity Monitoring.",{},"\u002Fdocs",{"title":895,"description":954},"docs\u002Findex","hlmztODRAzuxeqE0I-mO24xbgJojxGm1g0EbLpC3i8A",{"id":846,"title":847,"body":961,"description":887,"extension":91,"meta":987,"navigation":93,"path":889,"seo":988,"stem":891,"__hash__":892},{"type":8,"value":962,"toc":981},[963,965,967,969,971,973,975,977,979],[11,964,847],{"id":852},[19,966,856],{"id":855},[15,968,859],{},[19,970,863],{"id":862},[15,972,866],{},[19,974,870],{"id":869},[15,976,873],{},[19,978,877],{"id":876},[15,980,880],{},{"title":79,"searchDepth":80,"depth":80,"links":982},[983,984,985,986],{"id":855,"depth":80,"text":856},{"id":862,"depth":80,"text":863},{"id":869,"depth":80,"text":870},{"id":876,"depth":80,"text":877},{},{"title":847,"description":887},1785415893465]