If you are considering using this tool for any purpose, you must understand the severe risks:
Below is a realistic rule definition as used in MRChecker CCN2 configuration: mrchecker ccn2
rule_id: "CCN2_RISK_007"
name: "Cross-Currency Basis Consistency"
description: "Checks that cross-currency swap valuations match individual currency legs"
source_tables:
- ccs_valuation
- fx_forward_curve
conditions:
- type: "numeric_equality"
left: "ccs_valuation.net_pv_usd"
right: "ccs_valuation.leg1_pv_usd + ccs_valuation.leg2_pv_usd"
tolerance: 0.05 # 5 cents
tolerance_type: "absolute"
filters:
- "trade_status != 'CANCELLED'"
severity: "ERROR"
action_on_failure: "BLOCK_BATCH"
docker pull mrchecker/ccn2:latest
docker run mrchecker/ccn2 check --target google.com:80
Security standards often require proof of network segmentation. MrChecker CCN2 generates auditable logs showing that VLAN A cannot access database port 3306 on VLAN B, while API port 443 remains accessible. If you are considering using this tool for
mrchecker ccn2 /local/hello
Expected output:
Sending Interest for /local/hello
Received Data (size=128 bytes)
Validation: OK
RTT: 12.3 ms
The software targets specific payment gateways known for weak AVS (Address Verification System) checks. It sends a pre-authorization request. The gateway's response determines the result: mrchecker ccn2