Skip to content

akaasjager/vFense

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

vFense

Join the chat at https://gitter.im/vFense/vFense

An Open-Source Cross-Platform Patch Management and vulnerabiltiy correlation tool.

Basics on how vFense server works.

The vFense agents retrieves the metatdata of all of its updates through it's assigned repositories. ( Just the metadata )

  • This metadata is than sent to the vFense server.

  • Once the server receives all of the application data from the agent, it than begins to correlate the data against vulnerability data and place the data into the appropriate collections.

  • During the processing of the application data, vFense will verify if the files already exist locally or if it needs to retrieve the updates from the urls that are within the metadata.

What happens when you install an update to an agent.

  • The install operation is placed into the server queue.
  • Once the agent checks in, the agent will retrieve all operations from it's queue.
  • The agent will see the operation to install an update.
  • The agent will than try to retrieve the update from the vFense server.
  • If the agent was able to download the file successfully from the server, the agent will than verify the md5 that the server gave it against the md5 it generated locally.
  • If the download or the md5 failed, the agent will than try to retrieve the update from the repositories it originally communicated to.

About

An Open-Source Cross-Platform Patch Management tool.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript 59.5%
  • Python 31.2%
  • HTML 5.5%
  • CSS 3.2%
  • PHP 0.5%
  • Go 0.1%