Required before assessment
Requests should identify the company, contact, assets, purpose, and confirmation that the requester has authority to submit the systems for review.
Authorization policy
Security work must be authorized, scoped, and safe. This policy explains the boundaries Kintsubyte follows before reviewing any system.
Share an asset you own or are authorized to test. Public validation comes first; deeper checks require signed scope.

Direct answer
Kintsubyte only reviews systems that you own or are explicitly authorized to submit. Scope is confirmed before assessment begins, and disruptive or third-party testing is not performed unless the responsible owner has clearly approved it in writing.
Policy details
Requests should identify the company, contact, assets, purpose, and confirmation that the requester has authority to submit the systems for review.
Denial-of-service testing, social engineering, physical testing, destructive exploitation, and third-party systems are excluded unless explicitly scoped and authorized.
Next step
Share an owned or authorized asset. Kintsubyte starts with non-destructive public checks, then scopes remediation, retesting, or deeper signed review only where useful.
Contact Kintsubyte
Send the company, asset URL, and scope context. Kintsubyte will review public exposure where authorization is clear and reply with confirmed findings or recommended scope.