Comparison Overview

microdronespictures

VS

Shavon Via Photography

microdronespictures

25984 Sand Canyon Rd, Santa Clarita, CA, 91387, US
Last Update: 2025-12-13

Engineer-built. Stuntman-operated. What sets our operators apart from the rest? They have experience. They are 2nd unit directors, stunt coordinators, and Hollywood stuntmen. They fully understand film: how a set works, how things should be shot, what a production needs, and most importantly, what looks good from the air. On set it is crucial for a flying camera team to not only understand what's going on, but how things work. We have that covered. On the engineer side we have full factory backing from microdrones. This means that the very people that pioneered the technology are the ones that personally build, modify and upgrade our drones. This ensures that we not only have technology that works flawlessly, but is top of the line, not available to the public, and far more technologically advanced then any other U.A.V. in the film business. microdrones pictures microdrones pictures is doing what others can’t do: Offering services based on the very best technology out there - the systems of microdrones Germany. Our symbiosis allows us to achieve outstanding, repeatable results. We're not talking individually-built, semi-professional quadrocopters - our entire fleet is 100% backed by microdrones headquarters in Germany and their factories in China and Russia to ensure top-notch quaility down to the smallest chipset. Together we can make sure that we're always at the edge of possibilities. Ferdi Fischer, head of microdrones-pictures: 'It took us a long time til we found the right approach to enter the high professional aerial cinematography business based on unmanned and remotely piloted platforms. For more than 3 years, we are working closely together with microdrones which opened up a completely new perspective for us to capture action scenes and other spectacular aerial footage. Our engineers put extreme efforts in upgrading the core systems of microdrones in order for us to be able to offer incredible aerial shoots for affordable budgets.'

NAICS: 541
NAICS Definition:
Employees: 1
Subsidiaries: 1
12-month incidents
0
Known data breaches
0
Attack type number
0

Shavon Via Photography

None
Last Update: 2025-12-17

Professional Photographer Studio. Specializing in wedding photography with a flare. We shoot in the moment to capture the love and emotion. But, We also know how to pose for those cherished moments that you will want for years down the road. So, you will get the best of both worlds. We also love portraits and photograph them in the same manner. So whether you like candidate portraits or posed. The studio is very well trained and experienced in both areas.

NAICS: 541
NAICS Definition:
Employees: 1
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/microdronespictures.jpeg
microdronespictures
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
https://images.rankiteo.com/companyimages/shavon-via-photography.jpeg
Shavon Via Photography
ISO 27001
ISO 27001 certification not verified
Not verified
SOC2 Type 1
SOC2 Type 1 certification not verified
Not verified
SOC2 Type 2
SOC2 Type 2 certification not verified
Not verified
GDPR
GDPR certification not verified
Not verified
PCI DSS
PCI DSS certification not verified
Not verified
HIPAA
HIPAA certification not verified
Not verified
Compliance Summary
microdronespictures
100%
Compliance Rate
0/4 Standards Verified
Shavon Via Photography
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Photography Industry Average (This Year)

No incidents recorded for microdronespictures in 2025.

Incidents vs Photography Industry Average (This Year)

No incidents recorded for Shavon Via Photography in 2025.

Incident History — microdronespictures (X = Date, Y = Severity)

microdronespictures cyber incidents detection timeline including parent company and subsidiaries

Incident History — Shavon Via Photography (X = Date, Y = Severity)

Shavon Via Photography cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/microdronespictures.jpeg
microdronespictures
Incidents

No Incident

https://images.rankiteo.com/companyimages/shavon-via-photography.jpeg
Shavon Via Photography
Incidents

No Incident

FAQ

Shavon Via Photography company demonstrates a stronger AI Cybersecurity Score compared to microdronespictures company, reflecting its advanced cybersecurity posture governance and monitoring frameworks.

Historically, Shavon Via Photography company has disclosed a higher number of cyber incidents compared to microdronespictures company.

In the current year, Shavon Via Photography company and microdronespictures company have not reported any cyber incidents.

Neither Shavon Via Photography company nor microdronespictures company has reported experiencing a ransomware attack publicly.

Neither Shavon Via Photography company nor microdronespictures company has reported experiencing a data breach publicly.

Neither Shavon Via Photography company nor microdronespictures company has reported experiencing targeted cyberattacks publicly.

Neither microdronespictures company nor Shavon Via Photography company has reported experiencing or disclosing vulnerabilities publicly.

Neither microdronespictures nor Shavon Via Photography holds any compliance certifications.

Neither company holds any compliance certifications.

microdronespictures company has more subsidiaries worldwide compared to Shavon Via Photography company.

Both microdronespictures company and Shavon Via Photography company employ a similar number of people globally.

Neither microdronespictures nor Shavon Via Photography holds SOC 2 Type 1 certification.

Neither microdronespictures nor Shavon Via Photography holds SOC 2 Type 2 certification.

Neither microdronespictures nor Shavon Via Photography holds ISO 27001 certification.

Neither microdronespictures nor Shavon Via Photography holds PCI DSS certification.

Neither microdronespictures nor Shavon Via Photography holds HIPAA certification.

Neither microdronespictures nor Shavon Via Photography holds GDPR certification.

Latest Global CVEs (Not Company-Specific)

Description

Zerobyte is a backup automation tool Zerobyte versions prior to 0.18.5 and 0.19.0 contain an authentication bypass vulnerability where authentication middleware is not properly applied to API endpoints. This results in certain API endpoints being accessible without valid session credentials. This is dangerous for those who have exposed Zerobyte to be used outside of their internal network. A fix has been applied in both version 0.19.0 and 0.18.5. If immediate upgrade is not possible, restrict network access to the Zerobyte instance to trusted networks only using firewall rules or network segmentation. This is only a temporary mitigation; upgrading is strongly recommended.

Risk Information
cvss3
Base: 9.1
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Description

Open Source Point of Sale (opensourcepos) is a web based point of sale application written in PHP using CodeIgniter framework. Starting in version 3.4.0 and prior to version 3.4.2, a Cross-Site Request Forgery (CSRF) vulnerability exists in the application's filter configuration. The CSRF protection mechanism was **explicitly disabled**, allowing the application to process state-changing requests (POST) without verifying a valid CSRF token. An unauthenticated remote attacker can exploit this by hosting a malicious web page. If a logged-in administrator visits this page, their browser is forced to send unauthorized requests to the application. A successful exploit allows the attacker to silently create a new Administrator account with full privileges, leading to a complete takeover of the system and loss of confidentiality, integrity, and availability. The vulnerability has been patched in version 3.4.2. The fix re-enables the CSRF filter in `app/Config/Filters.php` and resolves associated AJAX race conditions by adjusting token regeneration settings. As a workaround, administrators can manually re-enable the CSRF filter in `app/Config/Filters.php` by uncommenting the protection line. However, this is not recommended without applying the full patch, as it may cause functionality breakage in the Sales module due to token synchronization issues.

Risk Information
cvss3
Base: 8.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Description

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Model Context Protocol (MCP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious MCP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered automatically without any user interaction besides opening the project in the IDE. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

Risk Information
cvss3
Base: 7.7
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Zed, a code editor, has an aribtrary code execution vulnerability in versions prior to 0.218.2-pre. The Zed IDE loads Language Server Protocol (LSP) configurations from the `settings.json` file located within a project’s `.zed` subdirectory. A malicious LSP configuration can contain arbitrary shell commands that run on the host system with the privileges of the user running the IDE. This can be triggered when a user opens project file for which there is an LSP entry. A concerted effort by an attacker to seed a project settings file (`./zed/settings.json`) with malicious language server configurations could result in arbitrary code execution with the user's privileges if the user opens the project in Zed without reviewing the contents. Version 0.218.2-pre fixes the issue by implementing worktree trust mechanism. As a workaround, users should carefully review the contents of project settings files (`./zed/settings.json`) before opening new projects in Zed.

Risk Information
cvss3
Base: 7.7
Severity: HIGH
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Description

Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10 relates to Storybook’s handling of environment variables defined in a `.env` file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the `storybook build` command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly) in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than `.env` files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible. Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, either prefix the variables with `STORYBOOK_` or use the `env` property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

Risk Information
cvss3
Base: 7.3
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L