Skip to main content

Velum Edge 0.9.1

Velum Edge team
Velum Edge team
Velum Edge

Velum Edge 0.9.1 adds a guided first run for new users and a screen for resetting a forgotten password, puts firm limits on bulk and CSV operations, tightens a number of permission and account checks, and improves how CrowdStrike and LinkShadow findings are matched to assets.

New​

  • Getting-started guide. A new user is walked step by step from an empty account to their first reviewed scan: create a tenant, add a sensor, connect an integration, create a scan template, schedule it, run a scan and review it.
  • Password reset screen. The link in a password reset email now opens a screen where you set the new password. Reset emails are only delivered when email sending is set up for the deployment.
  • Report retention. A deployment can have generated reports deleted after a set number of days. It is off by default. Files that nothing refers to any more are cleaned up automatically.

Improved​

  • CSV import takes at most 1,000 rows and checks the whole file before writing anything: a file with an error imports nothing.
  • CSV export writes a value that would start a spreadsheet formula as text, so opening an export cannot run a formula.
  • Bulk edit and delete take at most 1,000 assets per request and refuse a malformed list of assets.
  • Reports: a tenant can have at most 10 reports waiting or being generated at once. A deployment can change the limit.
  • Coverage settings are checked before they are saved. A scope filter the asset search rejects is refused instead of breaking the coverage screen.
  • List searches treat % and _ as ordinary characters everywhere.
  • Vulnerabilities: opening a vulnerability shows exactly its own findings.
  • Wizard: findings are refreshed as soon as an analysis finishes.
  • Dashboard charts: asset aggregations are limited in size and time span.
  • Subnets: a subnet mask must be in CIDR form to be stored or counted.
  • Uploads of up to 128 MB are accepted only by the endpoints that need them.
  • The server runs on updated libraries.

Fixed​

Asset correlation​

  • A LinkShadow finding for a phone is no longer merged into the Windows machine that held the same DHCP lease.
  • A LinkShadow finding with a generic host name is matched on its directory name.
  • A LinkShadow match on address alone is rejected when the candidate asset runs a different operating system family.
  • A LinkShadow finding without an address of its own no longer clears an asset's private IP.
  • A LinkShadow finding that groups two machines sharing a name is matched one machine at a time.
  • A CrowdStrike finding no longer updates an asset that belongs to another agent because of a shared name or address.
  • CrowdStrike records both the primary and the connection MAC address.
  • Every integration adds each network adapter it knows to the shared MAC address field, leaving out addresses that do not identify a machine.

Scans, reports and assets​

  • Merging assets moves only the pending scan changes of the same tenant.
  • An isolated scan whose source file cannot be stored leaves no task or partial file behind.
  • Report and template names are cleaned when saved and in the downloaded file's name.
  • Asset snapshots and reports release their search resources when they finish or fail.

Security​

  • Turning on two-factor authentication from a signed-in session asks for the password and signs out every other session.
  • Accepting an invitation requires a valid name and a strong password.
  • Verification emails are limited per account, and a new link replaces the ones sent before it.
  • A global role can only be granted, removed or edited by someone who holds all of its permissions.
  • The last active administrator can no longer lose user management through a role change, role edit or role deletion.
  • Account notifications reach only the user managers of the Organization where the event happened.
  • Viewing a tenant's Wizard now requires the Wizard Results read permission, which the built-in tenant roles include.
  • Permission checks were tightened for reading user records and individual fields. Only fields a tenant created can be edited or deleted, and a new asset can no longer be given values the system manages.
  • Sign-in checks the password before it reveals anything about the account's state, and records the last login only when sign-in succeeds.
  • Errors returned when an asset cannot be created no longer include internal details.