webforge.
Webforge products
peckr.Database activity monitoring

See who accessesyour data and how

Peckr brings Oracle, SQL Server and PostgreSQL audit events together. Detect suspicious activity, investigate data access and send alerts to your SOC.

What the product delivers

Less manual log reconciliation

Search user activity in a common event structure across Oracle, SQL Server and PostgreSQL. Follow an alert to its related events.

Rules that fit your operations

Account for service accounts and sensitive tables. Test new rules against historical events before enabling them.

Visibility into monitoring gaps

Track event flow, source health and channel errors. Receive alerts when monitoring may have stopped.

Product strengths

Test a rule before enabling it

Replay a condition against recent events. Peckr shows matches and examples without creating operational alerts.

Anomalies with an explanation

Compare operation counts with an account’s usual activity. Each alert shows the observed volume, baseline and amount of deviation.

Monitor the monitoring system

View silent sources, agent health, queues and delivery errors in the console. Your team can investigate where visibility was interrupted.

Capabilities

Unified audit across three databases

Collect supported Oracle, SQL Server and PostgreSQL events. Search by database, user and action; available fields depend on audit settings.

See it in a demo

Product interface

Current light interface of Peckr — demonstration data
Peckr — light interface
Current light interface of Peckr — demonstration data

A screenshot of the current local version with demonstration data.

Business use cases

Access to sensitive data

Mark important tables and investigate account activity. Retain related events, analyst conclusions and a report for the selected period.

Privilege and audit changes

Receive signals about suspicious changes. Enable Oracle and PostgreSQL snapshots to compare available security settings.

Tune rules before rollout

Test your rule on historical events, review matching examples and refine its conditions. Enable it for the agreed sources.

Who the product is for

For SOC and security teams

Identify actions requiring investigation, their sources and how to send alerts into your existing response workflow.

For DBAs and IT operations

Check whether database audit data is arriving, which components are running and where event delivery has broken down.

For internal auditors

Collect events, privileged actions and source data completeness for a selected period.

Deployment and integrations

Deployed in your infrastructure. For each database, we agree on audit settings, permissions, the agent or collector, and delivery method. Peckr analyses incoming events without proxying user SQL queries. Monitoring coverage depends on collection settings.

OracleSQL ServerPostgreSQLSIEM / CEFLDAP / Active DirectoryEmail / webhook

Getting started

01

Choose one database and use case

Agree on the database system, audit scope, collector permissions and delivery method. Define a test event and expected result.

02

Check events and rules

Connect the source, assess field completeness and test agreed rules. Label sensitive objects and review detections.

03

Verify delivery and reporting

Check an alert in your channel, source health and a period export. Use the results to decide whether to expand the pilot.

Product questions

Need technical details?
Let's discuss your architecture and requirements.

Why use Peckr if we already have a SIEM?

Peckr normalises audit events from different databases, adds source and rule context, and supports investigation. Alerts go to your SIEM for the existing response workflow.

Which databases and collection methods are supported?

Oracle: Unified Audit through a collector or file audit through an agent. PostgreSQL: supported logs through an agent or Vector. SQL Server: SQL Server Audit events from Windows Event Log through a forwarder. We verify settings and field coverage during onboarding.

How does behavioural analysis work?

The platform compares hourly operation counts with an account’s historical profile. After a learning period, alerts show the size of a deviation. This complements rules and still requires analyst judgement.

Can we test a rule before enabling it?

Yes. Replay events from the past hour, day or seven days without operational alerts. Up to 50,000 recent events are checked; the interface indicates when the selection is capped.

Does Peckr block SQL queries?

No. The platform passively analyses audit events. Your team or a connected system decides how to respond. We assess collection methods and database load during deployment.

What will the demo show?

We follow an action on a sensitive table through detection, analyst review, alert delivery and reporting. For your database, we agree on the source, audit settings and validation criteria.

From database event to investigation

Review a database event, the rule it triggered and a report. Choose a data source and agree on evaluation conditions in your infrastructure.

A database event and the triggered ruleAlert delivery and source monitoringA report and pilot criteria

No mailing lists. Only a response to your request.